|
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
|
|
| e.fail error from QODBC redordsets (ADO) |
| Author |
Message |
|
|
| Posted : 2006-05-06 05:22:31 |
I have a VB6 app that has been running sucessfully with QuickBooks 2004 and QODBC for a couple of years now.
The customer recently replaced the PC, so I reinstalled QB2004 and the App, but I had to download the l;atest version of QODBC (V6)
Now the app gets "E.FAIL" errors whenever it accesses the QODBC recordset (ADO recordset)
PLEASE DOES ANYONE HAVE ANY CLUES? (I'm crossing the Atlantic tommorrow, and I need to get this fixed first.)
David |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-05-06 18:57:07 |
Try changing the ADO cursor type to:
Const adUseServer = 2
oRecordset.CursorLocation = adUseServer
And just in case you try switching everything to adUseServer, please be aware stored procedure calls like sp_tables only like adUseClient cursor types.
|
|
|
|
|
|
| Posted : 2006-05-09 04:39:24 |
Thanks.
As I'm now back in Canada, I'll have to set up a system here to test it all on. I'll let you know if this doesn't fix it, though.
I did have another thought thought - I found that accesses on the Customers recordset worked OK. The problem was just with the ServiceItems recordset. Could this mean that the registration didn't work and QODBC thinks it's still in evaluation mode?
What ARE the restrictions in evaluation mode - just 30 days and 100 writes? There used to be restrictions on the tables you were allowed to access. Have those restrictions been removed?
David |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-05-09 07:53:07 |
| The 30 day evaluation works with all tables. I also recall that the e.fail error can be caused by NULLs, removing the NULL columns from the SQL Statement also fixed the problem. |
|
|
|
|