We are converting an existing application that used QODBC v4 to v6 to see if our application will still run.

We downloaded the 6.0 trial product from your website but when we attempt to update an EmployeeEarning record in a QuickBooks 2004 database file, using the following SQL statement:

"Update EmployeeEarning set PayrollInfoEarningsRate = 130.67 where payrollinfoearningspayrollitemwagereflistid = '180001-1140390656' and Listid = '20001-939784292'"

v6 now returns the following QODBC error: "[QODBC] Error parsing complete XML return string."

A lot has changed since QODBC v4 and v6, but the most important thing to remember is that "Error parsing complete XML strings" errors are because the column order is out of sync to what QuickBooks requres. This can be found by using:

sp_columns EmployeeEarning

The statement:

Update EmployeeEarning set PayrollInfoEarningsRate = 130.67 where PayrollInfoEarningsPayrollItemWageRefListid = '180001-1140390656' and Listid = '20001-939784292'

should be:

Update EmployeeEarning set PayrollInfoEarningsRate = 130.67 where Listid = '20001-939784292' and PayrollInfoEarningsPayrollItemWageRefListid = '180001-1140390656'

I ran the following test with my data your QODBC v6.00.00.150:

Update EmployeeEarning set PayrollInfoEarningsRate = 20 where Listid = '280000-1045709626' and PayrollInfoEarningsPayrollItemWageRefListid = '50000-1045536336'

and it updated without an error.

Note: If you don't immediately see the change, try doing:

SELECT * FROM EmployeeEarning unoptimized