>>>I am converting 10 FoxPro 2.6 systems to VFP and have a questions concerning databases and tables. The 10 systems have several tables in common, that I want to combine into one major look-up table. The concept I would like is that when a system needs data for lets say cage codes, it would go to the main table and check for data validity. But since the one table is used by 10 systems it cant belong to any one DBC. I would like some referencial integrety, but since the table cant belong to one system only I dont know how to accomplish this. I am posting this here in hopes that someone has figured a way to accomplish data validity for a lookup table that needs to be used by several systems. I hope this makes sense... And any suggestions will be welcome.
>>>
>>>TIA
>>
>>As I understand the only problem is to apply RI to separate free table which will be common for many systems. I guess the way to resolve it is following:
>>1. Create identical table inside DBC.
>>2. Run RI builder.
>>3. Go to generated code and replace (or replace whole stored procedure) with appropriate free table name.
>>4. If you're not going to rebuild RI in future, you can remove DBC table; else keep it (it will not hurt you).
>
>Could he not build a seperate DBC with all the lookup tables used by the apps...

Since I was the original poster, I would like to respond by asking how does that help with referential integrety across DBC's?