>>IMHO, 4 Yes
>>
>>MartinJ
>>
>>>Sorry for the short answers
>>>
>>>1 Yes
>>>2 No
>>>3 Yes (no additional fees to MS)
>>>4 No
>>>5 Yes
>>>
>>>Good luck!
>
>With just one line of code you make VFP9 almost totally compatible with VFP6:
>SET ENGINEBEHAVIOR 70

SET ENGINEBEHAVIOR 70 should be renamed to SET WRONG RESULT ON!

There was a very good reason why the engine behavior was changed in VFP8 and VFP9. The SET ENGINEBEHAVIOR command was introduced as a short time band aid, so that the wrong, not ANSI-SQL compliant SQL statements which were accepted in VFP6, did not raise errors. However, if you don't correct the SQL statements and change SET ENGINEBEHAVIOR to 80 or 90, you risk getting wrong results.