John,

"Jumping in" is what UT is all about. Feel free to jump in with questions, comments or solutions on any thread. I haven't yet written an application where I could see a need for more than one DBC. A while back someone talked about an app with over 600 tables, and I know he/she used several DBCs. But perhaps someone else will jump in with a situation that requires 2+ DBCs.

Barbara

>Barbara,
>
>PMFJI, Would you normally use only one DBC for an application? When would you want to use more than one DBC in an application?
>
>Thanks
>
>John
>
>>Eddie,
>>IMHO, if you are merging data, then go with 1 DBC. Each DBC has to be loaded separately, and your code must always be aware which DBC is open. If you want information from more than one DBC then you will have to deal with cursors and temporary files.
>>
>>If you are keeping each of the companies' data separate, then you might consider running your EXE in 3 areas with separate but identical DBCs for each area.
>>