Hello,

I am trying to get access to QB (2007) from our SQL server via a Linked Server, which may then be used by DTS/Stored Procs, called from a website

based on articles, DCOM seems like the best approach for multiple concurrent users...

To that end I've gone through the DCOM configuration, but it seems incomplete (only half works)...

How I'd like it to work:

QB2007 as a service (using srvany) - this can run as any user, if desired
ODBC connection using QODBC driver, connecting to QB2007 via DCOM
SQL Server 2000 connecting to Linked Server via ODBC connection

IIS website running sprocs which communicate to QB via linked server

(reason for this being that sprocs will provide atomic transactions between local SQL DB and QB, and QB as a service removes scripted logins and cleartext passwords)

So far, I've gotten QODBC installed, and when QB2007 is running
 (user instantiated, haven't gotten srvany set up yet),
 Query Analyzer/Enterprise Manager within my console session can access the QODBC linked server beautifully

however when I attempt to access QODBC linked server via QA/EM from a remote/network station, I get errors (800070005)...

I am happy to define specific user accounts for the roles (running QB as a service, etc)...
but I'm not sure which accounts need access where... the examples all focus on allowing IUSR access, but I'm not connecting to the ODBC from the website.

ideas?

thanks,
-Scott

What would be required (file/DCOM security, accounts, etc) for a Windows Service (on the QB workstation with QODBC) to access the ODBC connection string?... preferably without requiring QB to instantiate (but as it seems such an option doesn't exist) or to allow QB to run as a service accessed by QODBC?

Thanks,
-Scott