>I have an existing large application which uses about 40 free tables. I'm thinking of moving them into a DBC (in order to eventually be able to use triggers) and would appreciation some advice about what it will involve.
>
>I know that there are many advantages (referential integrity, long field names, etc.) but what is involved in a basic conversion before trying to take advantage of those new features? That is, if I simply convert free tables to a DBC and do nothing else, then to what extent will that require changes to my existing code for reading, writing, searching, SQL queries, etc.?
>
>Once that conversion is done with minimal downtime, I can explore the new options that are available to me....

To convert your existing app, the only thing you should need to do is make sure the database is opened as needed. If your code avoids CLOSE DATA, then opening it on start-up should do the trick.

Tamar