havw you looked into the Errors collection that is provided by DAO? That is
where your error will be buried.... the error you see is the one from DAO.
The collection will also contain (at a minimum) one error from the ODBC
driver and one error from the original source database engine.
--
MichKa
the only book on internationalization in VB at
http://www.i18nWithVB.com/
"Frank Boettger" <frank.boettger_at_t-systems.de> wrote in message
news:9n0k0o$aem$1_at_news.sns-felb.debis.de...
> Hi everybody :-)
>
> i've been looking the whole day for a solution for the following problem
> (and obviously i didn't find any):
>
> i'm working on a oracle (oracle8i version 8.1.6) database with a ms-access
> 97 frontend. Severall tables have quite complicated restrictions for what
> values (or better combinations of values) can be inserted (updated) into
the
> columns. Therefore, i've been writing several (before update-)triggers to
> ensure valid data entering. If something doesn't fit, those triggers raise
a
> userdefined exception. This way it's much faster and easier to ensure
valid
> data than to check with ms-access.
> So i thought, fine, one doesn't need to check within ms-access, one's
> getting an odbc error anyway, and then one could display a error message
> box. But now, in the sub Form_Error, i'm just getting those two errors:
> 1) one general "ODBC-call failed" (error 3146)
> 2) one error 7786 (which is an ms-access-error raised by the "failing"
> trigger)
> Anyway, i don't have a chance to determine which of my userdefined oracle
> errors is responsible for that. If i let access display the errors
(through
> setting the response for sub Form_Error to acDataErrContinue), directly
> after this error 7786 it will display a error message box describing my
> userdefined error. That's not of much help, because i have to react
> differently on different userdefined errors.....
>
> Any ideas?
> Thanks in advance,
>
> Frank
>
>
Received on Mon Sep 03 2001 - 14:16:07 CDT
