>Thanks Larry!
>
>That's exactly what I was looking for... I went throught the steps above and everything seems to be fine. Both systems read the file and all I needed to do was rebuild a couple views and locate the free table when I first modified some forms in development (dataenvironment was looking for it).
>
>Are there any issues I need to be aware of by using my using a free table as my base table for the application like indexing, etc. ?
>
>Renoir

As a free table you can't create PRIMARY key indexes on it. You can create CANDIDATE key indexes and use them as if they were PRIMARY. The only difference is that PK information is stored in the DBC. You can't create persistent relations with the free table as the target or source. That doesn't stop you from setting relations in code (SET RELATION). Triggers and rules can not be defined on free tables. This can be a problem if you use triggers to handle things like referential integrity.

Truthfully, I don't think you'll have a problem. While all of these are nice when working with a DBC, you can live without them.

God luck!