jmev7 wrote:
> I know why this is happening to me. It's due to a database password
> on an MS Access file. I can put code in each page that calls the
> database and redirect the user to the log in page, but I was
> wondering if I could trap this error and cause it to be dealt with as
> I would a 404 error. Is there any universal way to trap this error?
>

"Bob Barrows [MVP]" <reb01501@NOyahoo.SPAMcom> wrote in message
news:uYr0jzmjGHA.4652@TK2MSFTNGP05.phx.gbl...
> jmev7 wrote:
>> I know why this is happening to me. It's due to a database password
>> on an MS Access file. I can put code in each page that calls the
>> database and redirect the user to the log in page, but I was
>> wondering if I could trap this error and cause it to be dealt with as
>> I would a 404 error. Is there any universal way to trap this error?
>>
> One way would be to use an include file that performs the database
> connection.
> Another would be to use a custom error page:
> http://www.aspfaq.com/show.asp?id=2335
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>