>Opinions, comments, general feelings on simple question.
>Should I have one big DBC or two medium DBCS in one big system with many users?
>One with all tables (Lookups and Data)? Or two separate ones. Data tables in one DBC, lookup tables in the other. The system usually involves opening only one or two forms at the most (multiple tabs).
>
>Speed, integrality, optimization, standardization (whatever that is). Any thoughts

Working with one DBC is always easier, IMO. However, I often split them for several reasons:

1) Sometimes one needs to be opened exclusive to do heavy maintenance on a few certain tables often.
2) I often keep separate DBCs that contain only non-changing lookup tables in read-only server directories. This minimizes any chance for data/index corruption.
3) Size. You'll start noticing performance hits when DBCs become really large (25,000 records or so, maybe less). And they become awkward to work with when they reach several hundred tables and views.