>I am attempting to model a multi company solution. Each company is to have a
>complete copy of the DBC named BCSCompanyName. Each time I create a company Xcase allows me to 'rename' the database and respecify where the output is to be put. So far so good. There are a couple of tables that are shared between all of the companies and reside in a CommonData folder. Since they have relationships with other tables in the DBC I needed to put them into my Base DBC as well as opposed to making them free tables or giving them their own dbc. When I create a new company these tables already exist in the CommonData folder - and thus I get a bad backlink error since these tables belong to another DBC.
>Any suggestions on what the best strategy might be in this situation?
>Further thought on this subject has led me to think that maybe these should be Free Tables - does that sound right? They are basically used for reference and will mostly be readonly.
>
>Mike
If they don't need to have extended properties like longfieldnames, caption etc and are not part of persistent relationships then sounds very reasonable to me. Probably in final product they'd even be included in exe.
Cetin