Try connecting with SQL Authentication (trusted_connection=NO) and see if it works. If it works, then you need to make sure that user who has logged on the computer, under whose account the COM object is created, has access to SQL Server. You can do it through SQL Enterprise manager.


>Thanks for your response; I've been traveling and just received your message. This same web user has been accessing the network for over a year while the COM process worked against FoxPro 2.x tables. It doesn't seem like a network rights issue. The problem seems to be creating a proper connect string for SQL. The string used used by the application (DSN and database plus trusted_connection=YES) doesn't work with the COM process.
>
>>>There are no special steps you need take to connect to SQL Server via COM component. Does that Network User, logged onto the computer running COM, have access to the network? If yes, you can use connect to SQL Server using NT/Windows Authentication with read-only rights to the SQL database. If Network access cannot be granted, you can use SQL Authentication to connect but your network admin has to open up TCP/IP port (generally 1433) and change some firewall settings for the SQL requests to come through.<<