FIX: SQL Passthrough does not map SQL_WLONGVARCHAR that are more than 255 characters in length to memo field types in Visual FoxPro

This article was previously published under Q279138
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
SQL Passthrough does not map SQL_WLONGVARCHAR fields that are longer than 255 characters from Microsoft SQL Server to memo field types in Visual FoxPro.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the latest service pack for Visual Studio 6.0.

For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed
To download the latest Visual Studio service pack, visit the following Microsoft Web site:
MORE INFORMATION

Steps to Reproduce Problem

Run the following from the Command window with the user having the appropriate permissions.

NOTE: You need to provide the actual servername, user identification, and password for your installation of SQL Server.
nConnection = SQLSTRINGCONNECT("driver=SQL Server;Server=servername;UID=UserName;pwd=StrongPassword;database=Northwind")? SQLEXEC(nConnection, "select * from customers where customerid='CACTU' ;for xml auto,elements", "cust_xml")BROWSE NOWAITSQLDISCONNECT(nConnection)				
After you run the code, the results appear in a cursor with one 255-character column. Because the size of this particular field is approximately 351 characters, Visual FoxPro should return the results to a memo field.
Properties

Article ID: 279138 - Last Review: 10/21/2013 03:37:48 - Revision: 3.2

  • Microsoft Visual FoxPro 6.0 Professional Edition
  • kbnosurvey kbarchive kbbug kbcodesnippet kbdatabase kbfix kbvs600sp5fix KB279138
Feedback