FIX: SQL Query Returns Different Result Set with Korean Window (157187)
The information in this article applies to:
- Microsoft Visual FoxPro for Windows 3.0
- Microsoft Visual FoxPro for Windows 3.0b
This article was previously published under Q157187 SYMPTOMS
A 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.
If the index field is required, then use the SET COLLATE command on the
Korean or German setting and build whatever indexes are needed in this
collating sequence for normal operations, such as relationship and seeks.
Before running a query, temporarily set the collation sequence to machine,
and execute the query, but don't order it. Then set the collation sequence
back to Korean, and do a query on the result set and ORDER BY the desired
order.
STATUS
Microsoft 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.
Modification Type: | Major | Last Reviewed: | 9/30/2003 |
---|
Keywords: | kbbug kbenv kbfix KB157187 |
---|
|