I am trying to write an invoice that has a few hundred lines using FQSaveToCache.

The problem that I'm having is that as the invoice grows, each query takes longer and longer to execute even though FQSaveToCache = 1.

I tried to process the invoice in batches of a hundred but the problem still exists.

I thought that when using FQSaveToCache, QODBC doesnt query QuickBooks until FQSaveToCache = 0 so why does it make a difference as to how many lines there are?

I currently do not have the Optimizer on will it help to turn it on for INSERT statements?

(I am using QuickBooks Pro 2007 and QODBC 7.00.00.214)

This is not quite what we had in mind when using QODBC. Yes, the QODBC optimizer should be on, but it makes no difference when doing INSERTs. What you need to do is to first create the first line of the Invoice and then add each invoice line to the newly created invoice as shown using the Plan B technique in:  Using ClassRefListID when inserting invoice lines

Here is what I tried.

I inserted the first record setting FQSaveToCache = 0, the next two hundred records I set FQSaveToCache = 1 and used the TxnID (SP_LASTINSERTID) of the first line. The problem still exists that as it loops through the 200 records it gets slower and slower. (after about 150 it takes almost 20 seconds to execute)

Thanks for the reply.

When I use FQSaveToCache = 1 does it query QuickBooks at all or is it stored until FQSaveToCache =0?

If it's stored why would it make a difference as to the number of invoice lines?