I’m having a problem with my QODBC dsn setup and I need help.  My situation is that my quickbooks file resides on Server1, and my Microsoft Access database and web code reside on Server2.  When I RDC into Server2 and open the Microsoft Access database, I can view the linked tables to the QuickBooks file using a “QuickBooks Timer” DSN.  However, when I try to do the same through the web code, I get the following code:

Microsoft JET Database Engine error '80004005'
ODBC--connection to 'QuickBooks Timer' failed.

While on Server2, if I go to my Administrative tools and open ODBC connections, I have a System DSN called “QuickBooks Timer” and this is the correct setup that I’m using through the MS Access.  However, when I go to start, all programs, QODBC Setup Screen, there is a “QuickBooks Data” DSN.  I can’t seem to get rid of this DSN and it doesn’t really exist on Server2.  I think it was an old one.  This may be interfering, but then again, my error looks like it’s trying to access the correct DSN.

Any Suggestions?

QODBC has its own method to talk to a copy of QuickBooks running anywhere in the world over the Internet, or over your local area network. This feature is built-in and requires no additional charge. You don't need QuickBooks 2006 for this to work, you just need to download and install our current QODBC driver release.

Using this feature allows you to set up multiple workstations with QODBC on a network to call a server or another workstation on the network (or over the internet) that's running one copy of QuickBooks.

See: I do not want to install QuickBooks on every machine. How do I setup QODBC Remote? for more.

Also, can you tell me what the error description is that corresponds to 80004005?

Thanks

See: How can I see QuickBooks data in a Internet Explorer Browser using Windows XP? and http://www.qdeveloper.com.au/forum.php?homeinclude=searchtopic&keyword=DCOM

80004005 means you're busted ... you can't RDC a web connection.

Ok.  I think I understand what is going on here now.  Please help me if I get this wrong or if there are any other potential ways of doing this.  My company QuickBooks file resides on Server1.  My web code and MS Access database resides on Server2.  I have a web app on Server2 that is accessing the MS Access database on Server2 and the MS Access database has a linked table to the QuickBooks Timer table on Server1.  I can connect to the tables in the MS Access database through my web app fine, and I can connect to the QuickBooks Timer table through the MS Access database fine, but I can't connect to the QuickBooks Timer table through MS Access by running a Query in my web app.

After reading your post, I see that for one, I need the Server Edition of QODBC, and I'm only using a evaluation version (testing to make sure this whole thing works before purchasing).

Also, it appears that I would need to use the remote connector because the DCOM Servers choice would not work since my web App and database resides on a different server in the network as the QuickBooks file, unless i left the QuickBooks file running on Server2.  Currently, QuickBooks is not installed on Server1 and only the file rests out there.  When the company QuickBooks file needs to be opened, it is done so on our secretary's local machine (Client1).

If we were to go down the remote connector path, which it appears we would have to, would we need to have the QuickBooks file always open on Client1?  Also, our secretary often needs the file in single user mode to run reports and do administrative stuff (she usually is working in the file all day).  Will that cause issues?  If the QuickBooks file needs to be in multi-user mode, than the remote connector would have to run on Client1 so she could switch it back and forth between multi-user and single-user because she does not have access to Server1 or Server2 to make the changes.

Is there any othe way to do this, or am I forced to make the decision to do it this way or search a different solution?  If you have any past experience in this or suggestions, they would really help, because this whole process is not very easy.

Basically if you're running Windows 2003, IIS can only work with data sources on the server itself. It will not work with a DSN that points to another computer. I have yet to see anyone crack this yet.

The simple solution is to have QuickBooks on Server2 that accesses the company file on Server1. The company file needs to be in multi-user mode in order for Server2 and Client1 to access it.

If QuickBooks can't be on Server2, then you would use the QODBC Remote connector to get to the QuickBooks running on Client1 or Server1.

In short, QODBC talks to QuickBooks and QuickBooks talks to the company file.

In my case, we have to have QuickBooks running on Client1 because our secratary doesn't have access to Server1 or Server2.  So, i fired up remote connector on Client1 and opened the QuickBooks file there.  I then went to Server 2 and checked the iBiz integrator thing and filled in the credentials.  I don't know if this is working and don't see a way to test this.  There is a test connection, but that's just testing the DSN connection to the file specified on the general tab, not the connection to the remote connector on client1.  When i go to my web app, I still get the same 8004005 error.  My web app is accessing the MS Access database, but the MS Access database doesn't really know to use the remote connector, i think.  It's still trying to just use the dsn connection directly to the file on Server1, i think.  Can you help me?  What should the settings be on the connection setup screen?  Also, I can't go to the programs-> QODBC driver for QuickBooks-> QODBC setup screen because this brings up the wrong set up.  I have to go to the programs-> QODBC driver for QuickBooks-> Configure QODBC data source-> Select System DSN tab to get the correct setup info.  Why is that?  Is that part of my problem?  Is there someone I could speak to to resolve this problem more quickly.  It has been a long time and we payed a lot of money to get this software working, but it doesn't seem to be working for us.

ok, that helped a little.  I got a connection now through the iBiz connector, but the connection string had to be modified just a little to work.  My new problem seems to be with running a MS Access query. I have tried and googled every possbile way to execute a query, including just typing out the query.  It seems to run other queries fine, but for some reason, it doesn't like the word 'join' or 'left'.  It has to be a QODBC thing because my asp code doesn't mind left joins on other tables with the regular connection string.  The code that it bombs on is the following:

  strQuery = "qGET_UNDETERMINED_STAFF"
  rs.Open strQuery, db, 0, 4

and the error i get is:

    Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
    [QODBC] Expected lexical element not found: <keyword>
    /updateProjectBudget3.asp, line 124

I tried executing another similar stored procedure and for some reason QODBC wants this <keyword> element.  What does that mean?  I don't have any columns with the word keyword at all and i don't think that is something with my code.  I believe it's a QODBC thing.  Please help.

The code for the stored procedure is:

    SELECT DISTINCT TimeTracking.EntityRefFullName
    FROM TimeTracking LEFT JOIN Staff ON TimeTracking.EntityRefFullName = Staff.QBName
    WHERE ((Staff.QBName) Is Null);

If I take out everything after the "From TimeTracking", it works fine.  It dies on the "LEFT JOIN" part. 

Sorry, I can't debug code for your tables, however if you want to do a LEFT OUTER JOIN you can use something similar to this:

SELECT DISTINCT TimeTracking.EntityRefFullName, Employee.Name,
Employee.FirstName, Employee.MiddleName, Employee.LastName,
Employee.EmployeeAddressAddr1, Employee.EmployeeAddressAddr2,
Employee.EmployeeAddressCity, Employee.EmployeeAddressState,
Employee.EmployeeAddressPostalCode
FROM {oj TimeTracking TimeTracking LEFT OUTER JOIN Employee Employee
ON TimeTracking.EntityRefFullName = Employee.Name}

which works on the Employee table in QuickBooks. Simply swap it to your Staff table.

Well, I guess I was confused about this whole thing.  I now realize that with the Remote connector, i'm not connecting to my MS Access database, but directly to the QuickBooks File database.  I was hoping to connect to the MS Access db because I have tables I want to join on and update in the MS Access file.  Is there a way to connect to the MS Access database and join with the QuickBooks' linked tables in the MS Access database?  Please advise or offer a suggestion on what I can do.

thanks.