Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What have they done to VFP9 querying?
Message
 
To
23/08/2005 03:31:05
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Network:
Novell 6.x
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01042667
Message ID:
01042998
Views:
26
Dear Tore Bleken,

Thank you very much for your reply.

Of course, I understand that is not a bug - that is a "feature" :)

But I cannot convert my tables into 1252 Codepage, because I have to still use FPW 2.6 application, which update back any my changes after the next upgrade.

But I still not understand why it was not possible to do some exceptions, for example codepages 437 and 1252 or something like this (for DOS+Windows+MAC) for any particular language... I hope that will be fixed or added into SP1...

P.S. During many years I could not find this wrong search... May be because I use Numeric and English alphabet in indexes?


>Hi Sergey,
>
>I hope you have understood that this is NOT a bug at all. Actually this WAS a bug which was fixed in VFP9, in older versions of VFP you could get wrong search results if CPDBF() and CPCURRENT() don't match. So I suggest you convert your DBFs, or you must live with the possibility of getting the wrong search results.
>
Previous
Reply
Map
View

Click here to load this message in the networking platform