>>>>>Are any data compatibility problems between VFP6 and VFP5? I mean, if I modify table/database structure in VFP6, or even create new table from scratch there, will it pose any problem working with this data from VFP5 application?
>>>>
>>>>So far, the only thing that's bitten me is when I used new VFP6 specific functions in a stored procedure; that's by no means the result of exhaustive testing, though.
>>>
>>>Great! One my client got into specific situation: they lost their VFP5 CD-ROM, and cannot buy nothing except VFP6 now: they should have something to do data maintenance.
>>
>>That I've done on both free tables and .DBCs with standard maintenance-type things including PACK, REINDEX, and VALIDATE DATABASE without a hitch so far; they should be careful if they're using it to do MODIFY STRUCTURE on tables that are a part of a .DBC interactively, which I haven't tested yet.
>
>Just don't COMPILE DATABASE or modify stored procedures from VFP 6, or the compiled code will be mismatched.

That's probably what the caused the problem I alluded to in my earlier message, where I had updated a stored procedure using some new functions from VFP6.