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 : Error parsing complete xml string when updating CreditCardChargeExpenseLineSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC SQL Support Forum

 New Topic 
 
 Post Reply 
[1]  
 Error parsing complete xml string when updating CreditCardChargeExpenseLine 
 Author   Message 
  Flash 
  
 Group: Members 
 Posts: 27 
 Joined: 2006-10-22 
 Profile
 Posted : 2007-01-19 09:58:23

I have no problem changing bill expense line memos but when I run the same sql on the creditcardchargeexpenseline table, I get this error and I'm not sure what this QODBC message means but it looks to me like the driver might be looking to change the creditcardtable instead of the creditcardchargeexpenseline table???

2007-01-18 17:48:33 QODBC Ver:  7.00.00.204 *********************************************************************************************************************
IsAService: False
SQL Statement: UPDATE "CreditCardChargeExpenseLine" SET "ExpenseLineMemo"=? WHERE "FQPrimaryKey" = ?
Error parsing complete XML return string (8)
Input XML:
<?xml version="1.0" encoding="ISO-8859-1"?>
<?qbxml version="6.0"?>
<QBXML>
    <QBXMLMsgsRq onError = "continueOnError" responseData = "includeNone">
        <CreditCardChargeModRq requestID = "1">
            <CreditCardChargeMod>
                <TxnID>F18ED-1146772354</TxnID>
                <EditSequence>1169142688</EditSequence>
                <ExpenseLineMod>
                    <Memo>sdfsdfasdfsdf</Memo>
                </ExpenseLineMod>
            </CreditCardChargeMod>
        </CreditCardChargeModRq>
    </QBXMLMsgsRq>
</QBXML>

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-01-19 12:02:18

Check the "Review SDK Messages" log in the QODBC Setup Screen for the SDK error why your update is not being excepted.

 

  Top 
  Flash 
  
 Group: Members 
 Posts: 27 
 Joined: 2006-10-22 
 Profile
 Posted : 2007-01-19 12:36:38

Here's what it says, but I'm sorry, Idon't know what it means?

20070118.203357 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2332).
20070118.203358 I 848 SpecVersion Current version of qbXML in use: 6.0
20070118.203358 I 848 QBSDKMsgSetHandler QUERY: Credit Card Charge
20070118.203358 I 848 QBSDKMsgSetHandler Request 1 completed successfully.
20070118.203358 I 848 MsgSetHandler Finished.
20070118.203358 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2332), ret = 0.
20070118.203358 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2332).
20070118.203358 I 848 SpecVersion Current version of qbXML in use: 6.0
20070118.203358 I 848 QBSDKMsgSetHandler QUERY: Credit Card Charge
20070118.203358 I 848 QBSDKMsgSetHandler Request 1 completed successfully.
20070118.203358 I 848 MsgSetHandler Finished.
20070118.203358 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2332), ret = 0.
20070118.203359 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2332).
20070118.203359 I 848 SpecVersion Current version of qbXML in use: 6.0
20070118.203359 I 848 QBSDKMsgSetHandler QUERY: Credit Card Charge
20070118.203359 I 848 QBSDKMsgSetHandler Request 1 completed successfully.
20070118.203359 I 848 MsgSetHandler Finished.
20070118.203359 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2332), ret = 0.
20070118.203359 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2332).
20070118.203400 E 848 XercesSAXErrorHandler Element 'Memo' is not valid for content model: '(TxnLineID,AccountRef?,Amount?,Memo?,CustomerRef?,ClassRef?,SalesTaxCodeRef?,BillableStatus?)' -- error at line 7, column 127 in XML data.
20070118.203400 I 848 MsgSetHandler Parser error, finishing.
20070118.203400 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2332), ret = 1.
20070118.203400 E 2332 RequestProcessor Process Request error = 80042500, There was an error when parsing the provided XML file.
20070118.203400 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2332).
20070118.203400 E 848 XercesSAXErrorHandler Element 'Memo' is not valid for content model: '(TxnLineID,AccountRef?,Amount?,Memo?,CustomerRef?,ClassRef?,SalesTaxCodeRef?,BillableStatus?)' -- error at line 7, column 127 in XML data.
20070118.203400 I 848 MsgSetHandler Parser error, finishing.
20070118.203400 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2332), ret = 1.
20070118.203400 E 2332 RequestProcessor Process Request error = 80042500, There was an error when parsing the provided XML file.
20070118.203400 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' starting requests (process 2332).
20070118.203401 E 848 XercesSAXErrorHandler Element 'Memo' is not valid for content model: '(TxnLineID,AccountRef?,Amount?,Memo?,CustomerRef?,ClassRef?,SalesTaxCodeRef?,BillableStatus?)' -- error at line 7, column 127 in XML data.
20070118.203401 I 848 MsgSetHandler Parser error, finishing.
20070118.203401 I 848 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2332), ret = 1.
20070118.203401 E 2332 RequestProcessor Process Request error = 80042500, There was an error when parsing the provided XML file.

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-01-19 12:43:06
The SDK is saying "Element 'Memo' is not valid for content model", I have logged the problem with the QODBC Software Engineer and will reply when the problem/bug is resolved. 

  Top 
  Flash 
  
 Group: Members 
 Posts: 27 
 Joined: 2006-10-22 
 Profile
 Posted : 2007-01-23 11:47:22
Sure hope they fix this fast because I just got QuickBooks 2007 so I could change the memo fields in credit card charges, checks, etc. Holding my breath for this... 

  Top 
  Flash 
  
 Group: Members 
 Posts: 27 
 Joined: 2006-10-22 
 Profile
 Posted : 2007-02-13 22:56:29
I downloaded version .207 but am still getting the error message. Was the credit card expense line issue fixed yet? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-02-13 23:26:33
No it has not been fixed yet. Once the problem has been resloved I will update this topic. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-04-12 08:21:44

The "Error parsing complete XML return string (8)" error has been fixed in QODBC v7.00.00.214, however there is another bug that will be fixed in the next version of QODBC (Build 215 or greater). The flag that should autocopy the ExpenseLineTxnLineID to the Output xml sent to QuickBooks was off a field. The work around before the fix is made is to include the ExpenseLineTxnLineID in the set section as in:

UPDATE "CreditCardChargeExpenseLine"
SET "ExpenseLineMemo"='test', ExpenseLineTxnLineID='4300-1071540741'
where TxnID='42FE-1071540741' and ExpenseLineTxnLineID='4300-1071540741'

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-08-08 09:38:23
Please update to QODBC Release v7.1.0.230 as this bug has been fixed (Release 7.0.0.215 Fixes). See: How can I get the latest version of QODBC?   

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to