Our TimeTracking table is completely blank and will not optimize properly.  I have looked through all the posts to determine a fix, but nothing has worked.  All of the other tables optimize perfectly, but since TimeTracking is our most important table, this greatly impacts our use for QODBC. 

We are using QB Enterprise 2007 7.0 and QODBC 7.00.00.214.

Here is how our trace log ends:

ISAMNextRecord
    0x001DB280 [ISAM]
    0x10936C68 [TimeTracking]
    Optimizer Passthrough: FALSE
    Optimized SQL 1:
    Optimized SQL 2:
    Elapsed Time: 00:00:00 Time Difference: 00:00:00.031 Building XML Request
    Elapsed Time: 00:00:00 Time Difference: 00:00:00.000 Waiting On QuickBooks
    Elapsed Time: 00:02:21 Time Difference: 00:02:21.454 Initial XML Parse
    Elapsed Time: 00:02:21 Time Difference: 00:00:00.312 Initial XML Parse - LoadXML Start
    Elapsed Time: 00:02:30 Time Difference: 00:00:09.000 Initial XML Parse - LoadXML End
    Elapsed Time: 00:02:30 Time Difference: 00:00:00.000 Find First Record
    ISAM_FIND_ERR S0000 00000 [QODBC] Error: %s
    ISAMNextRecordExit
ISAMGetErrorMessage
    0x001DB280 [ISAM]
    S0000 00000 [QODBC] Error: 1000 - There has been an internal error when processing the request.
ISAMCloseTable
    0x001DB280 [ISAM]
    0x10936C68 [TimeTracking]
    NO_ISAM_ERR 00000 00000
    OptimizeLoadEmptyTable: TimeTracking UpdateTime: 2007-07-10 16:09:57.000 (UpdateLastTimeModified)

Here is how the SDK log ends:

20070710.160918 I 2868 RequestProcessor ========= Started Connection =========
20070710.160918 I 2868 RequestProcessor Request Processor, QBXMLRP2 v6.0
20070710.160918 I 2868 RequestProcessor Connection opened by app named 'FLEXquarters QODBC'
20070710.160922 I 2868 RequestProcessor Opening the file in the DoNotCare mode.
20070710.160946 I 2844 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2868).
20070710.160947 I 2844 SpecVersion Current version of qbXML in use: 4.0
20070710.160947 I 2844 QBSDKMsgSetHandler QUERY: Host
20070710.160947 I 2844 QBSDKMsgSetHandler Request 1 completed successfully.
20070710.160947 I 2844 QBSDKMsgSetHandler QUERY: Company
20070710.160947 I 2844 QBSDKMsgSetHandler Request 2 completed successfully.
20070710.160947 I 2844 QBSDKMsgSetHandler QUERY: DataExtension Definition
20070710.160947 I 2844 QBSDKMsgSetHandler Request 3 completed successfully.
20070710.160947 I 2844 MsgSetHandler Finished.
20070710.160948 I 2844 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2868), ret = 0.
20070710.161000 I 2844 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2868).
20070710.161000 I 2844 SpecVersion Current version of qbXML in use: 6.0
20070710.161000 I 2844 QBSDKMsgSetHandler QUERY: Time Tracking
20070710.161000 I 2844 TimeTrackingStorage::DoQuery Setting iterator chunk size to 00000500
20070710.161130 E 2844 TimeTrackingStorage::DoQuery Failed to get an Interface ptr:  Source: .\src\TimeActFilter.cpp line #86 HRESULT=0x80004005
20070710.161134 I 2844 QBSDKMsgSetHandler Request 1 failed.
20070710.161138 I 2844 MsgSetHandler Finished.
20070710.161141 I 2844 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2868), ret = 0.
20070710.162338 I 2868 RequestProcessor Connection closed by app named 'FLEXquarters QODBC'
20070710.162339 I 2868 RequestProcessor ========== Ended Connection ==========

Please open one of the sample company files and advise whether a sample TimeTracking table will optimize correctly on your computer. If you haven't purchased a full version of QODBC, and are using the QODBC version supplied with the USA version of QuickBooks Enterprise 2007, you will need to contact QBES support directly for further asistance.

BTW: What payroll option are you using?

A sample TimeTracking table optimizes perfectly.  Perhaps our TimeTracking table has gotten too large?  When the optimization window ticker is working, it climbs to over 120,000 lines.  It would be nice if there was a partial optimization stored procedure, i.e. from 1/1/07 forward, in addition to the fullsync and updatesync options.  I've tried everything on the forum and have even rebuilt the data in QB.   

We are using the QuickBooks Enhanced Payroll service. 

Thanks for all your help.

You need to increase your Iterator or Chunk Size to 20,000. The Iterator or Chunk Size determines the size of the rowsets that are retrieved from QuickBooks. The maximum Iterator or Chunk size that can be set is 100000 (higher than that and it resets itself back to the default of 500).