[QODBC Desktop] QODBC Desktop: Cannot UPDATE CustomFieldInvoiceLineOther3–Other6 on InvoiceLine Table

Problem Description:

You are unable to update certain CustomFieldInvoiceLineOtherX fields on the InvoiceLine table via QODBC. The UPDATE statement fails silently or throws an error, while other custom fields (such as Other1 and Other2) work correctly.

Affected products: QODBC Desktop (builds after v357), QuickBooks Desktop
Expected outcome: You understand which InvoiceLine custom fields are writable via QODBC, the known bug number, and a workaround to restore full UPDATE capability.

Symptoms:

• An UPDATE InvoiceLine SET CustomFieldInvoiceLineOther3 = 'abc' statement fails or silently does nothing.
• CustomFieldInvoiceLineOther1 and CustomFieldInvoiceLineOther2 work fine, but Other3 through Other6 do not.
• The issue began after upgrading to a newer QODBC build - it worked in an older version (v357 or earlier).
• SELECT queries on these fields may still return data, but UPDATE does not write to them.

Cause:

A bug introduced in a QODBC Desktop release prevents UPDATE operations on the CustomFieldInvoiceLineOther3 through Other6 fields of the InvoiceLine table. These fields are no longer writable, while Other1 and Other2 remain supported.

Resolution:

1. Workaround: Downgrade to QODBC v357 (build 357). This version still supports UPDATE on CustomFieldInvoiceLineOther3–Other6.
1. Download QODBC v357: https://qodbc.com/download/builds/357/qodbc.exe
2. Close all applications that use QODBC or QuickBooks.
3. Uninstall the current (broken) version of QODBC.
4. Install the downloaded v357 build.
5. Reboot Windows.
6. Activate your CDKEY from the QODBC Setup Screen (About tab).
7. Test your UPDATE statement again. The custom field updates should work as before.
2. Alternative: Use Other1 or Other2 instead. If downgrading is not feasible, consider mapping your data to CustomFieldInvoiceLineOther1 or CustomFieldInvoiceLineOther2, which continue to work on all builds.

Additional Notes:

• This is a known regression from QODBC build v357 and later. If you are relying on UPDATE of CustomFieldInvoiceLineOther3–Other6, stay on v357 or earlier until a fixed version is released.
• Select queries are not affected. You can still read CustomFieldInvoiceLineOther3–Other6 via SELECT; only UPDATE is broken.
• Your existing license carries over to v357 - there is no need to reactivate or purchase a new CDKEY.

Example Scenarios:

Scenario 1 - Mapping external data to InvoiceLine custom fields:

A company maps external ERP custom codes to QuickBooks InvoiceLine lines using CustomFieldInvoiceLineOther3. After upgrading QODBC, their integration stopped writing. The workaround was to downgrade to v357 and restore the UPDATE statements.

Related Articles:

QODBC: Known Limitations on QuickBooks Table Field Support How to Download and Install a Specific QODBC Build

Keywords: