QODBC Optimizer and misc notes

NOTE:  (Abrar) Strange QODBC behavior can occur if the optimizer file is located in it's default folder, i.e. a folder in "appdata", which is a system folder. Remove this possibility for problems by creating your own folder, then setting the QODBC param Optimizer tab accordingly.

Dirty read mode should be checked so balance fields will be corrected  optimized.

Rebuild optimization files:

1. Remove any existing .opt files from optimizer data folder (typically C:\Documents and Settings\Administrator\Application Data\QODBC Driver for QuickBooks\Optimizer)

2. Rebuild cache by using VB Demo with the following commands (one per table)

sp_optimizefullsync <table name>

Tables that need to be cached for ForceField:

1, Terms

2. Customer

3. ShipMethod

4. Item

5. ItemInventory

6. Account

7. Template

8. Invoice

9. PriceLevel

 See this link for how to automate (i.e. make a batch process) the cache rebuild.

http://support.flexquarters.com/esupport/index.php?/Default/Knowledgebase/Article/View/2459/0/how-to-execute-sp_optimizeupdatesync-or-sp_optimizefullsync-for-selected-tables

See also:

http://support.flexquarters.com/esupport/index.php?/Default/Knowledgebase/Article/View/2392/0/qodbc-slow-or-fails-on-large-invoiceline-dataset

http://support.flexquarters.com/esupport/index.php?/Default/Knowledgebase/Article/View/2358/0/how-to-setup-qodbc-optimizer-and-where-are-the-optimizer-options

http://support.flexquarters.com/esupport/index.php?/Default/Knowledgebase/Article/View/2435/57/how-to-configure-qodbc-to-work-with-64-bit-ms-access