>>I think that you will just want to have a MTDLL server. As far as licenses, if your data is being published on the internet by a COM object, SQL server has a special license for this. I would check the SQL server site for details, or call MS to be sure what licensses you need to buy. Either way, your server config won't change your legal obligation to MS to purchase the correct type of license.
>
>Thanks for your response Erik;
>
>In this situation most users are on a LAN/WAN. If I get everyone to log into NT using the same user name it does what I want (but of course, that is not practical).

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.