It would be better to handle it at the client. Just add a javascript on_submit routine to check a local JS varialble to determine if this is the second event ... if so cancel the form's sumit action. This way the server database is not queried. In a message dated 10/30/00 2:23:43 PM Eastern Standard Time, [EMAIL PROTECTED] writes: << Since you are probably going to store the information from the form when they submit it the first time, why not add a flag field that identifies the action 'state' of a particular record. If each user is uniquely identifiable then just do a quick search on that identifier before inserting form data. If a record already exists for that particular id then disallow the new information. >> ------------------------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
