# Attribute id is required by quickbooksadodesktopupdate

**URL:** <https://community.cdata.com/t/attribute-id-is-required-by-quickbooksadodesktopupdate/602>\
**Category:** CData Drivers\
**Tags:** question, odbc, quickbooks-desktop\
**Created:** [January 18, 2024, 9:09pm UTC](https://community.cdata.com/t/attribute-id-is-required-by-quickbooksadodesktopupdate/602 "2024-01-18T21:09:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin](https://avatars.discourse-cdn.com/v4/letter/k/2acd7d/32.png) [@Kevin](https://community.cdata.com/u/Kevin)\
**Post date:** [January 18, 2024, 9:09pm UTC](https://community.cdata.com/t/attribute-id-is-required-by-quickbooksadodesktopupdate/602/1 "2024-01-18T21:09:44Z")

</div>

Quickbooks - ODBC call is failing when trying to update a column using a Passthrough query in MS Access. It appears to only fail when there are multiple records to update. Works fine with a single record.

SQL&nbsp;string looks like this:

UPDATE&nbsp;SalesReceipts

SET DepositAccount = ‘Checking’

WHERE Date=’2024-01-01’;

Persistent connection is ENABLED

---

<div class="post-metadata">

**Author:** ![Ethem\_Q](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/ethem_q/32/1997_2.png) [@Ethem\_Q](https://community.cdata.com/u/Ethem_Q)\
**Post date:** [January 22, 2024, 11:27pm UTC](https://community.cdata.com/t/attribute-id-is-required-by-quickbooksadodesktopupdate/602/2 "2024-01-22T23:27:03Z")

</div>

Hi @Kevin

From a quick test on our side, this issue cannot be reproduced with the latest version of the driver. Can you please clarify what version of the ODBC driver for Quickbooks are you using?

In case you have downloaded the latest version of the Quickbooks connector and are still seeing this issue when Updating the SalesReceipt table there might be more to this issue so in order to uncover the cause we will need you to reach out to the support team and provide a driver logfile with verbosity 3. To enable logging, set the Verbosity connection property to 3 and the Logfile property to a local path in your machine where the log will be generated (ex Logfile=C:/Users/User/Documents/CDataLogs) to once the error is reproduced.

Feel free to reach out at [support@cdata.com](mailto:support@cdata.com) or submit a support ticket [here](https://www.cdata.com/support/submit.aspx) &nbsp;with the details of the issue.