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.

>I have a VFP COM server that receives parameters from a web site and passes back a formatted XML string for display on the site. The COM object is on a box outside our firewall and has limited rights (read and execute, I think) o FoxPro 2x tables on the LAN server. This has worked fine for a couple of years (so long that I've forgotten exactly how I implemented it in the first place <g>.) This month, the data has been moved to SQL 2000. Somehow I'm missing something and haven't been able to establish a connection to the SQL server from the COM process. What user(s) and rights need to be added to the SQL database to accommodate the COM object? What's the optimum way to establish the SQL connection?