Richard -

Your question is timely because I was going to ask a similar one regarding using multiple DBCs. I don't know if this will answer your question. In my case I have a DBC which contains all the table information for a Judge's conference. But in considering future projects, I realize that some of the info being entered for the conference (e.g. Names/addresses, Job type, District, etc.) is the same info I'll need for designing a new leave tracking system or for financial info. That's when I started thinking "Hey, I don't really want one Godzilla DBC for everything." Then I started to realize I'm going to need a nubmed of DBCs whose data tables may intersect. I hadn't considered putting all the views in one DBC, but that's an idea.

Sylvia

>Dragan,
>
>I can understand the concepts of what you are saying...but I haven't been exposed to a real life example. Could you give me an example of a suit of apps which plug into each other? I think the closest I've come to this so far is my current app, but only because we've moved all of our client information into the accounting system, and because we need to invoice...but we're only just scratching the surface of what you describe.
>----------------
>>>Rick
>>
>>In a single app, no big reason. But imagine a suit of apps which plug into each other (or into a main app, whatever), and sure have some tables in common. Which DBC should the common tables belong to?
>----------------------
>>>
>>>I've been doing Fox for years, but I'm just finishing up my first major VFP app., so I'm not an expert in VFP/OOP/C-S. When would I want to use multiple DBC's in an app? What should I be aware of if/when I do? What are the benefits/dangers/hassles? What about maintenance and performance?
>>>