Hi Fabio,

we have run into numerous issues where the SQL we generate works in MSSql, but does not work in Visual FoxPro. Getting the two to work as much as possible alike is of tremendous importance in getting Visual FoxPro acceptance in the marketplace, as it makes upsizing to MSSql a relatively easy task.

Hank


- For old applications this behavioure have little importance;
- For new little applications, this behaviour have little importance;
- For new big applications, a serious developer cannot implement it into VFP,
but use directly a backend solid database.


I can do in a job day:
- upgrade 100 or more VFP complex query into MSSQL,
- downgrade 10 MSSQL very complex query into VFP,
- write only 1 workaround code for a object with event sequence with a bag,
without the absolute certainty it's exactness

Any problem with SELECT ( within VFP data size limits) can to be solved
with a little more work,
but bugs on events sequence is hard or impossible to solve.

The concept is simple:
- first VFPT fixing what a developer cannot do or found a workaround for do that
- next VFPT can fixing or enhance the rest.

Fabio