You've had some good suggestions so far. Another way would be to put a unique compound index on the studentID and courseID. Then if a user tries to insert a duplicate you get an ODBC error. On the error HTML page of the insert action you display a message saying they're already registered.
This has 2 benefits. 1) you don't have to do a search every time, so it's faster 2) it maintains data integrity by ensuring there are no duplicates Hope it helps. Dave. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Stein > Sent: Friday, June 07, 2002 9:59 AM > To: Multiple recipients of list witango-talk > Subject: Witango-Talk: Preventing Refresh > > > Is the something I can put into the Meta data section of a specific HTML > page that will prevent the user from refreshing the page. > > I have a result page after a course registration that if refreshed will of > course register them a second time for the same course. It messes up the > course count. > > Dan > -- > Dan Stein > Digital Software Solutions > 799 Evergreen Circle > Telford PA 18969 > Land: 215-799-0192 > Mobile: 610-256-2843 > FMP, WiTango, EDI,SQL 2000 > [EMAIL PROTECTED] > www.dss-db.com > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
