Pete, When the user submits the page where is the user sent? If he stays on the same page and the form stay populated you need to do some checks for change in a field before allowing the page to submit again. The better way is to clear the form or send them to another page. That's all client side.
On the server side: Is there a positive ID field such as SSN that can be picked up from the form? If so then test the database for existence of this and inform the user. Or (I haven't done this yet but am sure it will work) grab the session ID and set a flag or a cookie that is checked prior to updating the database. You could even give the user the option to resubmit the data and do an update with it overwriting the prior entry. If you can use some unique data from the form this is usually the better (IMHO). Some other factor to consider in which approach to take is if the client fills in the form say one or two days later or from another machine. Doug www.parsonstechnical.com Subject: Stopping repeating requests > Hi, > > I have a problem where a user enters data into a form and then submits this > to the server, which in turn wrights this content into a database. > > The problem I have is that if the user then refreshes the page via F5 then > it adds the same data in again. > > Is there any way to ensure that this does not occur. > > Any help would be greatly appreciated. > > Thanks > > Pete > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
