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
|
|
unspecified error when inserting a duplicate customer name |
Author |
Message |
jeff |
|
Group | : Members |
Posts | : 76 |
Joined | : 2006-06-03 |
|
Profile |
|
Posted : 2006-12-08 14:32:27 |
When inserting a customer with a duplicate name I catch the following exception:
Error: 3100 -The name "jeff100" of the list element is already in use."
Here is the message Log: 2006-12-07 19:24:45 QODBC Ver: 7.00.00.194 ********************************************************************************************************************* IsAService: False SQL Statement: insert into Customer(name) values('jeff100') 3100 - The name "jeff100" of the list element is already in use. Input XML: <?xml version="1.0" encoding="ISO-8859-1"?> <?qbxml version="5.0"?> <QBXML> <QBXMLMsgsRq onError = "continueOnError" responseData = "includeAll"> <CustomerAddRq requestID = "1"> <CustomerAdd> <Name>jeff100</Name> </CustomerAdd> </CustomerAddRq> </QBXMLMsgsRq> </QBXML> Output XML: <?xml version="1.0" ?> <QBXML> <QBXMLMsgsRs> <CustomerAddRs requestID="1" statusCode="3100" statusSeverity="Error" statusMessage="The name "jeff100" of the list element is already in use." /> </QBXMLMsgsRs> </QBXML>
Problem is that in my catch block, the exception no longer returns the correct error. Instead of saying that the name is already in use, I get "unspecified error". If I mess up the sql statement so that it doesn't parse I get back the correct error in my catch block. That proves that nothing is wrong with my systax. Any ideas why i'm getting unspecified error as opposed to the real error message? |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-12-08 23:21:37 |
Sorry, do you still get the Error: 3100 part? Did this work before? What changed? |
|
|
|
jeff |
|
Group | : Members |
Posts | : 76 |
Joined | : 2006-06-03 |
|
Profile |
|
Posted : 2006-12-09 04:05:55 |
Yes, it worked before. I figured out how to make the error message come back. Take off the dcom server checkbox and use the remote connector and suddenly the correct error comes back. Is this a bug? Other error messages come back when using the dcom servers just not this particular one.
I am using odbc driver version 7.00.00.194 |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-12-09 07:29:24 |
Sounds like a bug, I've reported it under Support Ticket ID: BR00000043. Thanks for letting us know. |
|
|
|
|