|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| MS SQL Server 2000 Linked Server issue using the QODBC optimizer |
| Author |
Message |
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-02-23 09:04:31 |
We're evaluating QODBC server edition, and trying to use it in a linked server environment with SQL Server 2000.
It appears some queries work fine using the OPENQUERY command, but other queries that use different tables return no rows, even though they work fine from the test VB application.
For instance, this query works fine:
SELECT * FROM OPENQUERY(QUICKBOOKS, 'SELECT * FROM CUSTOMER')
But this query returns no rows (even though there are invoices):
SELECT * FROM OPENQUERY(QUICKBOOKS, 'SELECT * FROM INVOICE')
Any ideas what could be causing this?
|
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-02-23 09:08:18 |
A linked server runs queries as multiple treads, and the QODBC optimizer is single user only. So you need to setup a different optimizer file for the SQL Server to use than the other disktop applications. To do this, set up a seperate System DSN (see: How do I create or configure a QODBC DSN? ) and specify a fixed location of the optimizer database folder for SQL Server to use (like: C:\Program Files\QODBC Driver for QuickBooks) instead of the default %UserProfile% method.
To repair the optimized Invoice table you can run:
SELECT * FROM OPENQUERY(QUICKBOOKS, 'SELECT * FROM Invoice VERIFY WHERE TxnID = "x"')
Note: You may need to create a new System DSN that includes an optimizer file off the root of your C: drive to successfully use the QODBC Optimizer with MS SQL Server 2000 or 2005. |
|
|
|
|