>>I have a client that's thinking of upgrading a program from Fox 3 to Fox 5 or 6. I have a couple questions I wanted to throw out to you guys, please.
>>
>>1) are there any "gotchas" that I should be aware of in making this transition?
>>
>>2) are there any compelling reasons I can give the client for upgrading? I have a feeling that the budget people aren't really going to want to spend the money (do they ever? :) ) so I want to tell them something that will really make them feel that it's absolutely necessary to make this transition.
>
>I moved from VFP3 to VFP6...
>
>Gotchas:
>- use must use NOFILTER in SQL statements in VFP6 to use the cursor results in a subsequent SQL query
>- VFP6 without SP3 can throw a lot of C5 errors
>- you lose Win3.1 as a platform
>
>Benefits (for me):
> - VFP6 SP3 is more stable that VFP3
> - SQL joins
> - faster reindexing time
> - native support for jpegs
>
>Man... what a weenie list I've come up with..

VFP 5 has the adjustable ROLLOVER clause to SET CENTURY, and the SET STRICTDATE y2k enforcement feature/gotcha. So just say the magic words "better y2k compliance" and there should be no need to say anything else :)