Problems can arise if you use new features in the database container: long names (field names of more than 10 characters), and especially triggers. Otherwise, if you postpone the new DB features, just putting tables into a database - without making any further changes - shouldn't cause you any trouble.
Regards, Hilmar.
>I've acquired a software project 9 months ago using VFP that accesses data using free tables as opposed to a database. Among the many clean-up activities we'd like to perform on this project is wrapping up all the free tables in a database and changing the many modules (exe's) of this project to use the database. Ideally, we'd like to change one exe at a time to use the database. Is it possible (and advised) to have one VFP-created exe access a set of free tables at the same time another VFP-created exe is accessing the same tables but through a database?
>
>Thanks,
>
>Valter
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
