Probably a bonehead question . . .
I'm trying to extract information from Err.Description within a form's Error event. Alas, Err.Description does not seem to be available from there.
I have a form that normally displays in DataSheet view. If a trigger on the Oracle back-end raises an error, I want my Access app to be able to parse out Err.Description and deliver a more user-friendly message than ODBC's message. I want to get the info about the message from the error coming back from Oracle, not by matching up error codes.
If I change the form to Single-Form view and put a Save button on it, I can capture Err.Description in the command button's Clicked() event, and then parse out what I need.
So if I must display this form in Datasheet view, where can I trap the ODBC error and display my user-friendly message?
Thanks!
Wayne
I'm trying to extract information from Err.Description within a form's Error event. Alas, Err.Description does not seem to be available from there.
I have a form that normally displays in DataSheet view. If a trigger on the Oracle back-end raises an error, I want my Access app to be able to parse out Err.Description and deliver a more user-friendly message than ODBC's message. I want to get the info about the message from the error coming back from Oracle, not by matching up error codes.
If I change the form to Single-Form view and put a Save button on it, I can capture Err.Description in the command button's Clicked() event, and then parse out what I need.
So if I must display this form in Datasheet view, where can I trap the ODBC error and display my user-friendly message?
Thanks!
Wayne