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
|
|
Customer Select Not Returning Values |
Author |
Message |
|
Posted : 2008-10-24 09:22:32 |
If I do a select query through QODBC the customer does not show up. If I look in the quickbooks UI the customer shows up. If I edit the customer in the quickbooks UI and save changes the customer then shows up when doing a QODBC select. How can I detect this problem and fix it using qodbc?
I can assume that it is caused by an error or corruption when doing an insert into the customer table. All of our customers are input using a qodbc query. Only a very small percentage have had this problem. Is there a way to trap for errors like a transaction would in SQL?
Thank you,
|
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2008-10-24 09:45:06 |
Not all edits to Customer rows are immediately detectable by the QODBC Optimizer. When a query isn't returning rows that should be there, try adding the UNOPTIMIZED tag like this:
Select * from Customer UNOPTIMIZED where BillAddressState = 'CA'
See: How do I setup the QODBC Optimizer? Where are the Optimizer options? for more on how the optimizer works. |
|
|
|
|
Posted : 2008-10-24 09:49:04 |
This is not just happening on new inserts some of these records have been in quick books for more than 9 months. I dont think the optimizer is to blame. |
|
|
|
|