>You can't bypass the SQL server license model just by moving a COM component to a common machine. 10 users accessing a database is still 10 users accessing a database. If the serveer is out of proc, or hosted in a MTS package, you can use DCOMCNFG to change the account that the server will impersonate while it operates, but I don't think that this helps the instance/connection situation.

This app is built on a VFP database and updates to SQL Server only when a save is done. (I can explain why I am using this model if you like.) Rather than having each user having a connection to SQL Server (or opening and closing connections to do saves) I wanted to send all requests to update SQL Server to a COM on the server that would maintain one open connection to SQL Server.

This a multi-thread out process COM. (I do not see a way to access a DLL sitting on the server, maybe I am missing something.) I tried setting the COM Identity property in DCOMCNFG but that only servered to allow access only to the user set in this property.