>How did you come to conclusion that code is run/suggested to be run in VFP6? I don't see anything in code that points to that.
"However, when SQL Server 7.0 began supporting Unicode characters, Visual FoxPro 6.0 failed because it could not accept Unicode characters."
The way I see it, this article is talking about 2 separate problems:
1. SQL7 and up can return Unicode characters. Because VFP6 can't accept these Unicode characters it "fails" in some unspecified fashion.
2. VFP7 and higher can accept Unicode from SQL7 and higher, but can't display it properly. Two workarounds are provided.
The "Status - This problem was corrected in Visual FoxPro 7.0." refers to Problem #1.
"The information in this article applies to:
Microsoft Visual FoxPro for Windows 7.0
Microsoft Visual FoxPro 8.0" - refers to Problem #2.
Most confusing.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
