[QODBC-Desktop] Troubleshooting - "Cannot update table ItemInventory Error 10004"
Posted by Jack - QODBC Support on 11 January 2016 10:21 AM

Troubleshooting - "Cannot update table ItemInventory Error 10004."

Problem Description:

I am trying to run an update on the Name field in ItemInventory. I've checked to see if it's updateable, and it is.

I get "Cannot update table ItemInventory Error 10004," and sometimes a window pops up after clicking OK, saying there is not enough memory to complete this task or similar. I was unable to get a screenshot of the error. I run the query with nothing else open overnight on a computer with 16GB of RAM. Memory should not be an issue. I need to be able to update part numbers in batches because there are over 30,000 parts. You can't do it one at a time.

Please help.

Solution:

Please put a limit on your update query & try again instead of updating all records at a time. Please try to update records in a small group/part.

QODBC is an ODBC driver. The QODBC driver works with all front-end applications which can access ODBC, some of which are faster than others. The QuickBooks interface SDK, which uses XML, is not the speediest file system available, but it does the job.

Please remember that QODBC is not a database but rather a translation tool. QuickBooks is a non-normalized flat file system with no indexes and will not perform like SQL Server or dBase files. Every transaction you request must be translated and communicated via large, complicated XML transactions to QuickBooks.

The QuickBooks application layer needs to process those XML requests. The larger the number of Records, the lengthier the XML request; therefore, QuickBooks may take more time and memory to process longer requests.

QODBC sends the request to QuickBooks (via QBSDK), and QuickBooks will process the request(the request is in XML format); if records are more in numbers, then QuickBooks may throw an "Out Of Memory" error.

(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please complete the captcha below (we use this to prevent automated submissions).