>Ouch. So it isn't possible to share data between 3.0 and 5.0/6.0 applications (at least not practically). I guess, in some rare cases, this would be a reason to use free tables as opposed to DBCs. I am assuming free tables are fine.(?)
>
>
>
>>>>>Do you know if it is the same for 3.0 to 6.0 conversions?
>>>>
>>>>3.0 to 6.0 will have the same problems as 3.0 to 5.0. The stored procedures in your DBC will be recompiled and will not be accessable in 3.0.
>>>
>>>How does this work when there is data out there being used? Not data included in the project, but data out there being accessed by VFP 3.0 executables. When a VFP 6.0 executable accesses the DBC, it recompiles stored procedures?
>>
>>Not in runtime. You'll get a error... "Compiled in previous version", if I remember correctly. If you open the DBC EXCLUSIVE, then VFP 6.0 will recompile it. But, then it isn't accessible in 3.0. VFP 6.0 can read the 5.0 binary files (re: the compiled code), so you don't have this problem.
Right. You won't have problems with free tables because there is no code in them.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer