Kevin,

If you run into contention issues, it is still possible to create a scheme where each COM server has its own DBC as well. Basically it's often helpful to think of each COM server as a "user".

I assume you have some reusable code to create the DBC copy when an app starts up. One approach might be to create a little table of instances where there is one record per instance. Each record corresponds to a subdir where a copy of the DBC can be made. So, let's say COM server #3 starts up. It traverses the little table looking for a record to lock (sort of like a semaphor). If it locks record #3, it also uses subdir .\dbc_copies\3\ for example.

-- Randy

>Interesting article -- I think I will use a remote view!! The only drawback on using a remote view is that it is a web application and I have read that sharing a remote view can lead to some contention issues (in all my desktop apps, the users get there own copy of the remote view DBC).
>
>There will only be 2 to 4 COM servers (using webConnection), so I don't know if the contention issue is serious or not for this scenario.