|
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
|
|
| Bill Entry from Access/SQL to Quickbooks |
| Author |
Message |
|
|
| Posted : 2006-04-22 09:32:23 |
Using the following code when activated by a button click the code will often times give the error of "Incorrectly built XML string" or "Insert on LInked Table Bill" but then after clicking button a second time the transaction will be entered into Quickbooks successfully. I have this scenario occurring with 2 of my clients. Any ideas?
Jim
strsql = "INSERT INTO BillExpenseLine (ExpenseLineAccountRefListID, RefNumber, ExpenseLineAmount, ExpenseLineMemo, FQSaveToCache) " & _
"Values ('" & strExpenseLineAccountRefListID & "', '" & strRefNumber & "', " & strAmount & ", '" & strmemo & "', 1)"
DoCmd.RunSQL strsql
strsql = "INSERT INTO Bill (VendorRefListID,APAccountRefListID,TxnDate,DueDate,RefNumber,TermsRefListID,Memo) " & _
"VALUES ('" & strVendor & "','" & strAPAccountReflistID & "','" & strTransdate & "','" & strDueDate & "','" & strRefNumber & "','" & strTerms & "','" & strMemoheader & "')"
DoCmd.RunSQL strsql
|
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-04-22 12:32:53 |
| Is the application connected to QuickBooks via a QODBC "auto-login" method? There can be a lot of modal panels that get in the way in QuickBooks. Other than that, you will need to look at the QODBC trace file to see how the XML strings are being incorrectly built, see: How do I turn on the trace log? for more. |
|
|
|
|