Help in design/threading

Hi all,

I have got a problem in designing the lowermost layer. Actually since we
are going to deploy our software on windows 98, we cannot have the luxury
of connection sharing (Am I wrong?). And since we wouldn't have more than
4-5 computers on the network and all of them must be able to work stand-
alone in case a netwrok problem occurs or the master computer fails (and
our clients usually do not have even the slightest knowledge of
computer), we have designed a pretty sohpisticated abstratction in terms
of connection management and fault tolerance which is done in our
Database layer so that business layer only receives data services and
doesn't know much about how it is done on on which connection (local
database vs. remote database). We have also placed merge replication
which solves inconsistencies of databases.

Now we want to create only one object of that class per machine (which
opens and holds on to two connections one to local database and one to
remote) and business layer tries to get the object if it is there and
create it if it is not there, so we wouldn't be opening a new connection
per each biz objects. How we could implement it:

1. Biz objects try to use GetObject(,"MyComponent.MyClass") which sadly
does not work for components written in VB.

2. Create our database component as single-threaded so that our clients
could share the object.

3.I couldn't think of anything else !:)
Thank you very much for your comments and suggestions, in advance.

Ali

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.