Hi

Have a client with 3 stores which have to report sales tax separately, so 3 company files.

The stores share the same product range ~ 12 K items which are Sale Priced in our custom application including Sales Tax - the tax is deducted when we send to QB via QODBC to QB.

They have EPOS systems that have to use ex-tax prices as some items are taxed and others are not.

The UK Sales Tax just got dropped from 17.5 to 15 % and we need to update about 8 - 9 K items in each of the 3 company files.

Normally the Optimizer would help in speeding up the UPDATE WHERE data, but as there are 3 separate company files the ListIDs are different although the FullName are the same (SKU) and the optimiser would have to be re-loaded as the company files were swapped by the accounts person - not really possible to manage with a user.

When I run the Batch Updates I see the 'round trip' to QB every time, I assume to locate the ListID of the WHERE FULLNAME index item on the jump-in.

What I want to know is if I send an Update to QODBC with the WHERE clause referencing the ListID of the ItemInventory product will that stop the 'round trip' and speed up the update process.

Ok, the first thing, the QODBC Optimizer stores a different companyfilename.opt for every company file and will close and open the correct .opt file as you open and close connections. Even if all three company files were called "Fred" you can still create a different DSN for each company using a different .opt file location.

A UPDATE has to run a query first, locate the rowsets to update and then update the rows. Because the only correct way to ensure that the correct rows get updated, we have to run the query in realtime against QuickBooks. So the optimizer isn't going to help you as far as updates are concerned.

If you run:

sp_columns tablename

you will find the jump-in columns that allow QuickBooks to return immmediate results.

Hi Tom

So, just to be clear, you are saying that QODBC has to do a call to QB for every UPDATE query sent to the driver in order to construct the QB XML file, even though it knows the ListID of the item ?

If I submit direct to the SDK with an XML file it just goes straight into QB - which is an order of magnitude quicker than QODBC.

Thoughts ?