you can solve that with a single DBC and something like Stonfield database toolkit Arnon >my 2cents -- i'd use one dbc to hold all 'basic' tables (like your A/R) and then one for each separate module. only caution is if customers buy one module, decide they like it and buy another. can't overwrite original basic dbc.