The information in this article applies to:
SYMPTOMSQueries with filter criteria run through the Visual FoxPro ODBC (VFPODBC) driver could return fewer records than the same query run in Microsoft Visual FoxPro. CAUSEThe VFPODBC driver defaults SET ANSI to ON where the default for SET ANSI in Microsoft Visual FoxPro is OFF. This setting cannot be changed in the VFPODBC driver. RESOLUTION
To work around not being able to use SET ANSI OFF for partial matches, you
can either use wildcards in the SQL Select statement, or create an OLE
Automation Server in Microsoft Visual FoxPro to manipulate the data in the
Microsoft Visual FoxPro database.
Wildcard ExampleIn the example given in the Steps to Reproduce Behavior section below, replace the line:
with the line:
and the line:
with the line:
When the above lines are substituted into the sample code below, each
Browse window should have four records.
Note that the above workaround will not be fully Rushmore optimized. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0. MORE INFORMATION
In Drvvfp.hlp (the VFPODBC Help file), there are references to the SET ANSI
command being supported in the VFPODBC driver. While issuing this command
to the ODBC driver does not return an error, it does not affect the SET
ANSI setting.
Steps to Reproduce BehaviorRun the following from a program in Microsoft Visual FoxPro:
Both Browse windows should have no records.
Additional query words: kbvfp600fix
Keywords : kbcode kbVFp FxprgRushmore FxprgSet FxprgSql |
Last Reviewed: August 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |