Thanks for your suggestion Colin. I may try this one day but I have found a way that works now if javascript is disabled. What I did is I tried the http://metabuilders.com/Tools/OneClick.aspx[^] webcontrol. And it did (sorta) prevent multiple form submissions. Although I would get a strange behaviour where if the button was pressed more than once. It would perform the task I wanted performed once but refused to forward to a page after the process was complete. It would just sit on the page the form was submitted from. Submit could then be pressed again and viola 2 database inserts. In fact when I stepped through the code the Server.Transfer("Foo.aspx") line of code would execute but yet it did nothing to the web application. I then added a GUID validation to the page and it fixed the problem above. Now if the client hits submit more than once the task I need inserts to the database only once the GUID changes after the second button click and then the client is forwarded to a page saying their request has already been processed blah blah blah you hit submit more than once. Also the GUID validation prevents them from hitting back and re-submitting the form. So this seems to work fine for the "javascript disabled" folk. And for most normal people who leave javascript alone I used this solution http://aspzone.com/articles/207.aspx[^] Thanks again. Perhalps with Whidbey there will be something better in place.
