|
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
|
|
| Creditremaining is null |
| Author |
Message |
|
|
| Posted : 2008-06-03 01:42:38 |
Our application reads and writes to the credit memo tables as part of our application. Something has changed in that the Creditremaining field in the Creditmemo table is now NULL. Previously, the Creditremaining contained the remaining balance. The nulls are there regardless of how the credit memo was added (either through the QODBC or the QB GUI).
Has something changed in QB, or did we do something to change this behavior? Any help would be greatly appreciated.
Thanks - Karl |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-06-03 08:08:47 |
Check your optimizer setting for: 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" uses the slower method to get the data directly out of QuickBooks making sure you get the most current value for the requested fields. (Real Time is the previous method used).
See: How do I setup the QODBC Optimizer? Where are the Optimizer options? for more. |
|
|
|
|