OCI - How to find which column caused a bind error

From: News Postings <newspost_at_sandman.co.uk>
Date: 1997/04/10
Message-ID: <334D557D.7DBB_at_sandman.co.uk>#1/1


[Quoted] With deferred mode linking, obndrv/n/a do not return errors such as invalid characters in numeric fields etc. These errors are only returned on a subsequent oexec or similar call.

[Quoted] Is it possible to find out, after the oexec, which column actually caused the error?

[Quoted] obndra, with its array of column-level error codes, doesn't seem to help - these just don't seem to be set for bind-type conversion errors (presumably they are used for select-type errors). Neither does the parse error offset in the cda help - by the time a bind error happens it is just set to the end of the statement.

Help please!

James Clavering Received on Thu Apr 10 1997 - 00:00:00 CEST

Original text of this message