Richard
>>When would I want to use multiple DBC's in an app? What should I be aware of >>if/when I do?
1. You should segment your data when it makes sense to logically group data together. We always have a system DBC that has users, setup information ,data dictionary information. Then we segment our applications even further into discreet units. For instance we would have a GL database, AR database, PO database, etc. This makes it easier to add and remove modules.

2. I would like to have put my views in another DBC instead of with the main dbc. The best solution would be to create all views programitically whenever the app starts. The problem is the performance. A view can have literally dozens of entries into a dbc file which tends to be slow.


>>What are the benefits/dangers/hassles? What about maintenance and performance?

3. The benefit is that you can mix and match applications in a lot simpler fashion.

4. There is no performance issue at all (at least that I can find)

5. The only real danger/pain I have found is if you put your data in one DBC and views in another you need to open the data DBC first and then the view DBC.

Great questions.

Thanks,
Rod