Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : Release 7.0.0.211 FixesSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC Updates and Bug Fixes

 New Topic 
 
 Post Reply 
 Release 7.0.0.211 Fixes 
 Author   Message 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-02-19 08:46:05

Added the following options to the Optimizer tab of the QODBC Setup Screen.

  • Under "Keep my optimized data up to date as of:" added "The start of every new connection (with "Reload All Data" first)". This option will reload all the data in the queried table prior to requesting the data from the optimizer cache.
  • Also added options: "For balances and stock quantities:" the option "Nulls" - will return NULLs for all fields that cannot be kept in sync, "Dirty Reads" - means return the most current value that was loaded into the optimizer cache, and "Real Time" which uses the slower method to get the data but making sure you get the most current value for the requested fields. (Real Time is the previous method used).
  • And finally, "Optimize data after an Insert or Update" causes QODBC to do "Load Updated Data" after an insert or update in executed on a table.

Connection string values are:

  • "OptimizerAllowDirtyReads" = "N|D|R" - N = NULLs, D = Dirty Reads and R = Real Time (the default if not specified)
  • "OptimizerSyncAfterUpdate" = "Yes|No" (the default is No)

The following is a unofficial list of columns/fields affected by Null/Dirty Reads/Real Time as of March 27, 2007:- 

List Tables

Account

  • Balance
  • TotalBalance

Customer         

  • Balance
  • TotalBalance
  • CreditCardInfoCreditCardNumber
  • CreditCardInfoExpirationMonth
  • CreditCardInfoExpirationYear
  • CreditCardInfoNameOnCard
  • CreditCardInfoCreditCardAddress
  • CreditCardInfoCreditCardPostalCode

ItemInventory

  • QuantityOnHand
  • TotalValue
  • AverageCost
  • QuantityOnOrder
  • QuantityOnSalesOrder    

ItemInventoryAssembly

  • QuantityOnHand
  • TotalValue
  • AverageCost
  • QuantityOnOrder
  • QuantityOnSalesOrder

ItemInventoryAssemblyLine

  • QuantityOnHand
  • TotalValue
  • AverageCost
  • QuantityOnOrder
  • QuantityOnSalesOrder           

Vendor

  • Balance

Transaction Tables

Bill

  • AmountDue
  • IsPaid
  • OpenAmount

BillExpenseLine

  • AmountDue
  • IsPaid
  • OpenAmount

BillItemLine

  • AmountDue
  • IsPaid
  • OpenAmount

CreditMemo

  • CreditRemaining

CreditMemoLine

  • CreditRemaining

Invoice

  • AppliedAmount
  • BalanceRemaining
  • IsPaid

InvoiceLine

  • AppliedAmount
  • BalanceRemaining
  • IsPaid

PurchaseOrder

  • IsFullyReceived
  • PurchaseOrderLineReceivedQuantity
  • PurchaseOrderLineIsFullyReceived

PurchaseOrderLine

  • IsFullyReceived
  • PurchaseOrderLineReceivedQuantity
  • PurchaseOrderLineIsFullyReceived

Sales View
[Invoice]

  • Remaining
  • IsPaid

[CreditReceipt]

  • Remaining

SalesLine View
[Invoice]

  • Remaining
  • IsPaid

[CreditReceipt]

  • Remaining

SalesOrder

  • IsFullyInvoiced

SalesOrderLine

  • IsFullyInvoiced

VendorCredit

  • OpenAmount

VendorCreditExpenseLine

  • OpenAmount

VendorCreditItemLine

  • OpenAmount
 

  Top 
 New Topic 
 
 Post Reply 

Jump to