>> >> >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.
>
>Agreed.
>
>Now back to my response at the top of this message. You can't use the
>Pre-VFP version to update the data, and have the VFP version respect
>those changes. What you're describing, having VFP update both sets of
>tables, was never in question.


OK..No problem...once a feature has been coded in VFP, it is either removed or disabled in the old application, thereby forcing the user to use the new program...and all tables stay updated properly.

Craig