Best to use On Error Resume Next all the time?

Hi All

My subject question is more of a specific one in that is it best to have on
Error resume next on your pages so that your chosen DB (ie MySQL, MS SQL,
etc) doesn't blurt out an error message, which could have sensitive info
such as table names, db names, etc, to your ASP page?

I know there are the implications of me making sure that I trap the errors
with friendly messages myself, but is it common practise for you to do this
so that the more sensitive info isn't shown?

Rgds

Laphan

Re: Best to use On Error Resume Next all the time?

Laphan wrote:
> Hi All
>
> My subject question is more of a specific one in that is it best to
> have on Error resume next on your pages so that your chosen DB (ie
> MySQL, MS SQL, etc) doesn't blurt out an error message, which could
> have sensitive info such as table names, db names, etc, to your ASP
> page?
>
> I know there are the implications of me making sure that I trap the
> errors with friendly messages myself, but is it common practise for
> you to do this so that the more sensitive info isn't shown?
>
In my case: yes.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Best to use On Error Resume Next all the time?

Thanks Bob

Bob Barrows [MVP] wrote in message
news:egchpW9zEHA.1392@tk2msftngp13.phx.gbl...
Laphan wrote:
> Hi All
>
> My subject question is more of a specific one in that is it best to
> have on Error resume next on your pages so that your chosen DB (ie
> MySQL, MS SQL, etc) doesn't blurt out an error message, which could
> have sensitive info such as table names, db names, etc, to your ASP
> page?
>
> I know there are the implications of me making sure that I trap the
> errors with friendly messages myself, but is it common practise for
> you to do this so that the more sensitive info isn't shown?
>
In my case: yes.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Best to use On Error Resume Next all the time?

On Sun, 21 Nov 2004 13:05:00 -0000, "Laphan"
wrote:

>My subject question is more of a specific one in that is it best to have on
>Error resume next on your pages so that your chosen DB (ie MySQL, MS SQL,
>etc) doesn't blurt out an error message, which could have sensitive info
>such as table names, db names, etc, to your ASP page?
>
>I know there are the implications of me making sure that I trap the errors
>with friendly messages myself, but is it common practise for you to do this
>so that the more sensitive info isn't shown?

What we normally do is use On Error Resume Next on production code
pages, leave it off development pages. But there are a number of
pages where we deal with errors in the code. For example, you could
just ignore the error of an empty recordset and show nothing, which
might be confusing or rude for the end user, or program for it and
dsplay a friendly message. Or still be rude but without the
confusion, displaying "Your search failed to find anything, you
ignorant twit!" :)

Jeff

Re: Best to use On Error Resume Next all the time?

Thanks Jeff

Jeff Cochran wrote in message
news:41a3763d.2021141307@msnews.microsoft.com...
On Sun, 21 Nov 2004 13:05:00 -0000, "Laphan"
wrote:

>My subject question is more of a specific one in that is it best to have on
>Error resume next on your pages so that your chosen DB (ie MySQL, MS SQL,
>etc) doesn't blurt out an error message, which could have sensitive info
>such as table names, db names, etc, to your ASP page?
>
>I know there are the implications of me making sure that I trap the errors
>with friendly messages myself, but is it common practise for you to do this
>so that the more sensitive info isn't shown?

What we normally do is use On Error Resume Next on production code
pages, leave it off development pages. But there are a number of
pages where we deal with errors in the code. For example, you could
just ignore the error of an empty recordset and show nothing, which
might be confusing or rude for the end user, or program for it and
dsplay a friendly message. Or still be rude but without the
confusion, displaying "Your search failed to find anything, you
ignorant twit!" :)

Jeff