Bon733
|
| Posted: 09/22/2003, 8:00 AM |
|
Is there a better way to show a database error than the default sql error
shown on the page. Since my app contains foreign key constraints I would
like to present the user a more non-technical error message. Any ideas?
|
|
|
 |
DonB
|
| Posted: 09/22/2003, 11:52 AM |
|
In the relevant events (after Insert, Delete, Update) you can inspect and/or
modify the errors collection of the datasource (or even clear the collection
altogether). This means you can cleanup the error to simplify it or change
the behavior - such as generate a popup error or simply writing it to a log
somewhere.
--
DonB
http://www.gotodon.com/ccbth
"Bon733" <bon@nospam.com> wrote in message
news:bkn2qf$2h7$1@news.codecharge.com...
> Is there a better way to show a database error than the default sql error
> shown on the page. Since my app contains foreign key constraints I would
> like to present the user a more non-technical error message. Any ideas?
>
>
|
|
|
|
|
