Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

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

Forum : Customer Table not accessible #10057 errorSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v6 Forum

 New Topic 
 
 Post Reply 
[1]  
 Customer Table not accessible #10057 error 
 Author   Message 
  PHughes 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-16 
 Profile
 Posted : 2006-08-16 14:14:34
I am running version 6.00.00.155 of the QODBC Driver. When I try to access the CUSTOMER or ENTITY tables from MS Access I get an error " ODBC - Call failed. [QODBC] Error: 1000 - There has been an internal error when processing the request. (#10057)" Basically, I cannot display either of these tables. I do not get this error on any of the other tables. 

 
Paul Hughes 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-08-16 14:38:02

Try disabling "Use Case Sensitive RefNumber Searches".

   

 

  Top 
  PHughes 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-16 
 Profile
 Posted : 2006-08-16 18:51:14
Thank you, after applying this change the error has now gone. However, now it displays a table with no records in it. Any other suggestions? I have upgraded to the latest release of the software too just to be on the safe side. 

 
Paul Hughes 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-08-16 22:50:00
Changing this setting affects how MS Access sees the table structure. Delete the Customer and Entity linked tables and add them back again. 

  Top 
  PHughes 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-16 
 Profile
 Posted : 2006-08-17 09:21:34
As requested, I deleted the links and re-linked these two tables but got the same result: table displays with all of the field headings but there are no records. 

 
Paul Hughes 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-08-17 09:36:02
Check the tables using VB Demo. If there's still no data, try another company file. The Australian edition of QuickBooks has a nasty habbit of corrupting the company file if too many fields are inserted or updated at once. You may need to go back to a backup of the company file. 

  Top 
  PHughes 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-16 
 Profile
 Posted : 2006-08-17 09:50:47

VB Demo did not return any records either. Tried with the sample data and got data to display. I did already try backups of my company file going back several months but still the same error. Any other ideas?

 

 
Paul Hughes 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-08-17 10:05:09
You can try using "Rebuild Data"  within QuickBooks (under File | Utilities), but it sounds like the company file has been corrupted. 

  Top 
  CoolHockey 
  
 Group: Members 
 Posts: 2 
 Joined: 2007-10-15 
 Profile
 Posted : 2007-10-15 10:31:05

I'm having this same problem, except with the Invoice table.

I can open up the Sales Order table and Item tables without any difficulty, but I can't get into the Invoice table.  If I make a new QuickBooks company, I have no problem accessing the invoice table, which makes me think that the company file that I am using is corrupt.

I'm using Microsoft Access 2003, and QODBC 6.    I've tried Rebuild Data utility as well as the suggestion about unchecking the Case Sensitive RefNumber Searches box, which didn't help.

Is there anything else I can try?  Let me know if seeing the log would help.

Raja

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-15 10:46:39

Use VB Demo and try running:

Select * from Invoice unoptimized where TxnDate > {d'2007-01-01'}

 

  Top 
  CoolHockey 
  
 Group: Members 
 Posts: 2 
 Joined: 2007-10-15 
 Profile
 Posted : 2007-10-15 11:00:21

Hi Tom,

Interesting... it gave me an hourglass for a couple of minutes, and then started to return about 6000 records (ya, I know, they do good business) ;)

In Access, I also just tried:

SELECT *
FROM Invoice unoptimized where TxnDate > #01/01/2007#;

It took a minute or so, but it worked too!  Thank you so much.  Was it the unoptimized clause which made it work?  Or was it a timeout issue?

Thanks again,

Raja

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-15 15:47:10

The unoptimized tag forces the query to be run in QuickBooks, just in case your optimized table was corrupted. You can drop using the tag. Seems the real problem here is the number of invoices. Without the where TxnDate > #01/01/2007#; clause there are too many invoices before a timout. For large company files you shouldn't query all rows in a table. Transaction queries should be limited to a start from transaction date.

See: MS Access - ODBC Call Failed on v7 with Timeout Error and How do I setup the QODBC Optimizer? Where are the Optimizer options?  for more.

 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to