While updating records in a QB File, using VB .NET, this error came up towards the middle of the file.

What does this mean - the program was working and the ListID's are retrieved correctly so I am not sure why it would stop at this point.  Does it have to do with optimization.

The SQL Command it stopped on was:

"INSERT INTO PriceLevelPerItem(ListID, IsActive, PriceLevelPerItemItemRefListID, PriceLevelPerItemCustomPrice) VALUES('50000-1144944964',1,'310000-1146238368',5.9)"

Thanks

INSERT is used to add new records. If you want to actually update a PriceLevelPerItem row, then the statement format would look like this:

Update PriceLevelPeritem SET PriceLevelPerItemCustomPrice = 43.21, PriceLevelPerItemItemRefListID = 'F0000-933272656'  WHERE ListID = '30000-1197755980' AND PriceLevelPerItemItemRefListID = 'F0000-933272656'

Thanks - but the first thing I do is 'DELETE from PriceLevelPerItem' so the file is empty when I start - that way I can be sure to do INSERT and not UPDATE as part of my program.  What does this error mean?  How does QODBC create this error?  It would seem you reference to 'Update Start', and your response, is that you believe the system wants to perform an 'Update' and not an 'Insert'.  My program works through the first 100 items before this error is created, but stopped at different times during this initial build of the custom price file.  (I tried it 3 times to find patterns in the error).   We are investigating the PC we are working on as one cannot underestimate the power of a virus, or bad memory, when running these programs!  Yet, the clarity is how to distinguish these errors or find these error codes in a file so we can review the responses and how to solve them without writing to the forum.

Thanks again, Vic

The PriceLevelPerItem area is a very sensitive part of Intuit's qbXML SDK. We have done a lot of work to try make calls to this part of the SDK workable, however deleting everything and reloading the table isn't recommended.

You should check for the existance of the item and update it if applicable or create it if it doesn't.

To examine what's happenning within QODBC you can turn on the QODBC Trace log, see: How do I turn on the trace log?