The information in this article applies to:
SYMPTOMSA SQL SELECT statement with a WHERE clause returns an unexpected result set if Visual FoxPro for Windows is running under Hangeul Windows 95 (Korean Windows 95). Similar results have been reported when using German Windows 95 or German Windows NT. WORKAROUND
There are two ways around this problem. Use the HAVING clause instead of
the WHERE clause in the SQL SELECT statement, or issue the SET COLLATE TO
MACHINE command before executing the SELECT statement.
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem has been corrected in Visual FoxPro 5.0 for Windows. MORE INFORMATIONSteps to Reproduce BehaviorCreate two tables. The table structures are as shown below :Structure
Contents
Issue the following command:
Run Visual FoxPro for Windows 3.0b under Korean or German Windows 95 and
the query returns an empty cursor, but it returns the correct result set if
the query is executed under other Windows 95 platforms.
Additional query words: kbdse VFoxWin
Keywords : kbenv FxenvOs |
Last Reviewed: December 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |