>>Franck,
>>
>>First of all, once you add a free table to a DBC it is no longer a free table. Also, and this is just my personal preference, but I never set RELATIONships in the DBC, I do it in code with SET RELATION.
>>
>I'm curious as to why you do this. Do you handle referential integrity manually (programmatically) too? The referential integrity *engines* I know of require persisitent relations in the DBC so they know what tables to check.

There are a few reasons. First, a lot of tables here require relationships on concatenated keys which is a PITA to do visually.

Yes, I handle referential integrity manually because when I first started using VFP it was the first release of 5.0 and I found the referential integrity *engines* to be unreliable at best and I've never looked at them since. However, since I don't do relationships in the DBC this is moot.

Also, because there are still a lot of legacy apps here, in the new VFP apps I have to deal with relationships with free tables.

Lastly, and this is just a personal preference, I find it cleaner and more useful to see the relationships in code, especially when maintaining apps written by myself or other developers here.