>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.?

One gotcha that I tripped over a few times involved use of CREATE TABLE commands, say when creating some unrelated table for maintenance or metadata purposes. If you issue a CREATE TABLE command when a DATABASE is currently selected, that table will get *added* to that database, unless you include the FREE clause. If you're going to convert, you might use Code References to examine your whole project for instances of "CREATE TABLE" and insert FREE clauses where appropriate.

-- Randy