Exactly, I agree with you Ben.

Another possibility is to add new SYS function. For example

SYS(3102 [,.T.|.F.] )

Character index expressions are used (or not used) for optimization, if CPDBF()<>CPCURRENT()

Ladislav


>Hi Aleksey,

>A new SET command in VFP9 to keep compatibility is desirable (for >example "Set QryCodePageSensitive On/Off"). Actually, setting >EngineBehavior to 80 to keep the old query behavior functional is similar. >We don't care in some cases questionable query results will be got since we >are sure our existing code will get 100% what we want.

>In many cases it is difficult, if not impossible, for us to unify the >codepage of existing DBFs. For examples,
>- applications are running on a 24x7 basis and tables are large and will >take time to copy
>- tables are generated or being used by another applications in clients' >machine and are to be processed by our VFP application.
>...and so on

>We (our company) have spent a lot of time to make CpDBF() of existing >tables in client sites match CpCurrent() in an version upgrade of an >application, which has a large installation base and are being run in both >western and Asian countries. So far, we have not yet managed to solve all >the problems. I hope a new SET command eliminating the codepage problems >can be found in VFP9-SP1.


>Ben Tam