Ah, that's the best idea yet. Force the data integrity by the DB, then it doesn't matter what front end is doing the insert, the dupes just can't happen.
Good one, Dave. Todd >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. -------------------------------------------------------------- Todd Trann, B.E., B.Sc. [EMAIL PROTECTED] Programmer / Analyst ph (306) 966-2610 Student Affairs and Services fax (306) 966-5092 University Of Saskatchewan http://www.usask.ca/sas/ ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
