Re: Oracle ODBC Error handling

You will have to look at Access to suppress/control the error handling. Oracle returns the error to the client app (in this case via the odbc driver)... but the display of the error message is controlled entirely by Access and not by the database nor by the odbc driver. The driver returns the error to the client only when requested by the front-end (Access).

-sm

On 1 Sep 1997 06:49:15 GMT, "Diederik Klaassen" <dklaassen_at_lucent.com> wrote:

>Hello all,
>
>I am creating an application in Access 7.0 which is using an
>Oracle 7.3 database.
>The database model includes all kinds of referential integrity checking.
>For every screen I created on this database I have written all kinds of
>checking
>functions like :
> Before an inasert new: does the primary key already exist ?
> Before a delete: Are there any related records ?
>This all to prevent Oracle from showing a more or less cryptical error
>message
>(and Access one generic ODBC error message of its own).
>However, if I could suppress the Oracle message and intercept the
>errorcode,
>I would not have to do all these checking at first. I could just show a
>message
>and roll back the action.
>
>So, is there a way to suppress the Oracle and Access errors and to attach
>some
>customized errorhandling ?
>
> Thanks for the help,
> Diederik Klaassen
> dklaassen_at_lucent.com
>
Received on Fri Sep 05 1997 - 00:00:00 CEST