how to do an asp friendly error?

Monie · August 13th, 2004, 01:00 AM

well...in my database(ACCESS), i have made two field to be a "PRIMARY KEY".
When i do the testing by entering the same value to this field in my ASP form, this is the IE error page saying something about the PRIMARY KEY!

----------------------------------------------------------------------
Technical Information (for support personnel)
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC Microsoft Access Driver] The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.
/admin/insertClassroomInfo.asp, line 90

Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Page:
POST 55 bytes to /admin/insertClassroomInfo.asp
---------------------------------------------------------------------

but instead of the IE error reporting them, i want my own Error Reporting (errorReporting.asp) page to be displayed! with my own message writen inside it!

HOW TO DO THIS SO CALL AN ASP USER FRIENDLY ERROR PAGE????

Webforumz Staff · August 13th, 2004, 04:16 AM

Maybe we could do an article on this guys? (Sorry monie I don't know the answer myself, but I'm sure Rob, Catalyst and Smokie do...lol)

Rob · August 13th, 2004, 04:25 AM

Actually.... all this needs is a call to the database FIRST.... Select records with the matching key you want to insert. If there are any records returned, then you know that inserting a record would fail and raise an error.... you can handle it from there.

Webforumz Staff · August 13th, 2004, 04:37 AM

Like Rob says there's better ways to do it, but if you do want the error thing then read up on using:
On Error Resume Next

You can then check the ERR object to see if any errors have happened and write out a message or redirect to a page based on the error type/number.

Google it for samples, etc.

Smokie · August 13th, 2004, 04:43 AM

Well if you have access to the server and IIS, you can choose to not display errors to the user, or you can choose your own ASP page which runs when different errors occurs, or you can do this.

Insert this at the top of your ASP page:

Code:

<% On Error Resume Next %>

This will tell ASP to just skip over any errors, instead of halting execution and printing out a nasty error message.

Then after any ADO call that accesses the database, put the following lines:

Code:

If Err.number <> 0 then
  Response.Redirect "errorReporting.asp"
End If

You will want to put this after all ADO calls that communicate directly with the database. This includes ConnectionObject.Open, ConnectionObject.Execute, and RecordsetObject.Open.

Monie · August 16th, 2004, 10:37 PM

thanx smokie, that helps me alot

Webforumz Staff · August 17th, 2004, 04:07 AM

<blockquote id="quote" class="ffs">quote:<hr height="1" noshade="noshade" id="quote" />Originally posted by Sirkent
Maybe we could do an article on this guys? (Sorry monie I don't know the answer myself, but I'm sure Rob, Catalyst and Smokie do...lol)<hr height="1" noshade="noshade" id="quote" /></blockquote id="quote">

I'm more impressed that Rob, Catalyst and Smokie actually answered in the order I said their names [:P]