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.

Thanks again, much appreciated. Still both solutions use javascript. If javascript was disabled on someones browser on purpose it would render those solutions ineffective.

I appreciate your input. But that will not work because before the text can be changed to "Updating Now" the process I want to run once and once only has to finish. By then it is too late and the user will be able to jam away at the button multiple times.

Hello everyone, I am just curious what you guys have done to prevent a client from jamming away on a submit button on a webform? I have been googling away for a few alternatives but most articles and suggestions I have found involve javascript. Such as this. Although this is a terrific solution, it doesn't prevent anyone from being a shyster and disabling javascript and abusing a webform. This can especially be a pain when the form submission involves inserting into a DB. The result being multiple rows inserted. So there has be some sort of server side solution where if javascript is disabled the multiple form submissions can be ignored or prevented. My current idea is to forward the form submission to a page (after the webform is validated) that indicates the task is processing. But surely there have to be some other solutions. And I am curious about what you people have done for this situation. Or if you know of a good solution on the web that I haven't uncovered on google I would appreciate the link! Thanks, Shaun

Navin wrote: Follow the green alien Is that what that is? My wife has always called it the green poop. :laugh:

Sometimes it helps to uninstall and reinstall IE. That fixed a problem I had with IE one time.

I am looking for a way to authenticate a user from one web app to be able to access a seperate web app. For instance. I have http://localhost/WEBAPP\_B/ and it will deny all un-authenticated users. But the login form for http://localhost/WEBAPP\_B/ is on http://localhost/WEBAPP\_A/. So far I have tried setting the loginUrl (in Web.config) from WEBAPP_B to WEBAPP_A/Login.aspx and I get forwarded to it, but when i supply the credentials I just get forwarded back to WEBAPP_A/Login.aspx repeatedly. I am assuming the authentication cookie that is written is only good for WEBAPP_A and I remain un-authenticated for WEBAPP_B. So is it possible to create an authentication cookie from WEBAPP_A that WEBAPP_B will accept? Or is there a better way? Any advice or direction is appreciated! Thanks! -sb