>When developing West-Wind applications, I made the mistake of using a Multi-use com server instead of a single-use com server and a file that was supposed to be open was being closed by on of the other threads. Variables were losing values or there values were being changed. This Com server which is separate from the West-wind com server must be a single multi-use com server. We need to have one session table opened exclusively serving the data. This separate com server will prevent the data caching that was occuring with multiple single-use com servers.

Uhm, not exactly. You should use Single Use EXE servers. multi-use EXE servers will cause all sorts of problems with overlapping memory since the same instance is getting hit by multiple simultaneous requests.