B
brodym
Guest
Are you still able to reproduce this error, or are your runs always successful now? Did you capture any logs (ie ODBC trace) when the error was occurring? Could the data in your QAD databases have been changing while performing the load? As you may have surmised, this indicates that some sort of error occurred while fetching data. The exact problem could vary based on the cursor type being used and the ODBC API calls being used to fetch the data. To name a couple examples, it could result from attempting to select a row that has been deleted, or some sort of issue converting the data from the value returned by the database to the type requested by the application. To narrow it down further, you'll need to be able to capture an ODBC trace of the problem. Whenever possible, capturing a snoop of the problem is also very helpful ( www.datadirect.com/.../download-tools ). If you capture an ODBC trace of a working example, it might allow us to narrow it down a bit more, but we wouldn't be able to give you an answer with any certainty if you're no longer able to reproduce the issue.
Continue reading...
Continue reading...