Hi Xenophon,
I think Bruce's suggestion is reasonable ,the onsubmit won't be fire by all
the post back enabled controls. Instead of using the onsubmit event or
intercept the __doPostBack function, I think you can also consider just
disable the certain submit button after the user first time click it. Also,
the end user still can refresh the page to make multi post back submits. So
it is most important to also provide serverside transaction checking or
even in database level. Here are some tech articles and former threads
discussing on the similiar problem:
#How to prevent multiple clicks of a submit button in ASP.NET
http://aspzone.com/articles/207.aspx http://groups-beta.google.com/group/...amework.aspnet
/browse_thread/thread/7743c065b33c241d/33c3f7f4cc5f79a5?q=asp.net+prevent+pa
ge+multiple+submit&_done=%2Fgroups%3Fhl%3Den%26lr% 3D%26q%3Dasp.net+prevent+p
age+multiple+submit%26&_doneTitle=Back+to+Search&& d#33c3f7f4cc5f79a5
http://groups-beta.google.com/group/...amework.aspnet
/browse_thread/thread/6fab6a8261900df3/2d7bf741ea8c2024?q=asp.net+prevent+pa
ge+multiple+submit&_done=%2Fgroups%3Fhl%3Den%26lr% 3D%26q%3Dasp.net+prevent+p
age+multiple+submit%26&_doneTitle=Back+to+Search&& d#2d7bf741ea8c2024
HTH.
Thanks & Regards,
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)