>> >> Set up the VFP application to do things the VFP way...OOP, Data
>> Sessions,
>> >> etc. In the DBC, you'll have stored procedures that are called by the
>> >> triggers on the new tables. These triggers will automatically fire and
>> >> update the old FOXDOS free tables. Once the entire application has been
>> >> written in VFP, remove the triggers.
>> >
>> >This means that you'll require two copies of the data, right? One as
>> >the free tables that the Pre-VFP version can access (ahem!), and one
>> >with the tables managed through the .DBC.
>> >
>> >At this point, you wouldn't be able to use the pre-VFP version for
>> >updating (insert/update/delete) the information, because there'd be no
>> >way that these changes could show up in the VFP version automatically.
>>
>> Why wouldn't this work?? Map the fields to the VFP data, then save it to
>> the free tables in the Trigger methods.
>
>2.x can't see the tables, unless they're free tables. The triggers
>couldn't be fired through updates to the 2.x data.


That's right. The forms use data buffering and data sessions. VFP tables in the DBC are updated. When this happens, a trigger is fired. The trigger contains all the code needed to update the free tables, which can be seen by the FPD app. Once the conversion is done, the trigger code is removed.

Craig