|
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
|
|
| Quickbooks 2007 W/QODBC v6 |
| Author |
Message |
|
|
| Posted : 2006-12-19 06:04:32 |
We have been using QODBC v6 with Quickbooks 2006 for a while now. Last week we upgraded to Quickbooks 2007, but we are still using QODBC v6. Will this work for read/write? Currently we can successfully perform select queries with this setup, but when we try doing an insert it fails with the message, "[00000] [QODBC] This function requires the activation of the DESKTOP features." We also downloaded the QODBC v7 evaluation with the same result.
For version 6 of QODBC we did activate it. We also have read-only access mode unchecked in the QODBC option dialog. We have the read-write version of the driver, and it always worked OK with Quickbooks 2006.
What could be the issue?
Thanks for your help,
Kyle Stevens |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-12-19 10:37:30 |
| You have upgraded your QuickBooks to 2007, you now need to purchase a QODBC v7 CD Key for QuickBooks 2007 from your local sales office. Downloading and installed QODBC v7 doesn't upgrade your QuickBooks 2006 CD Key to 2007. |
|
|
|
|
|
| Posted : 2006-12-20 00:10:24 |
| Thanks. I purchased it and it now works... for the most part. It now isn't updating the invoice due date correctly, but I'll save that for a separate thread if I can't figure it out. |
|
|
|
|