Disable on button click

[Barry Gilmore]

Is there a way to disable a button after it is clicked?

I am trying to avoid having someone click on it twice while they wait for it
to process.

Thank you!

[Ken Dopierala Jr.]

Hi Bishoy,

That is what it is supposed to do. Let's say you are doing a credit card
payment. It makes sure the user can only click once. Then after processing
is done they are redirected to a success or failure page. It also lets the
user know that they can only click the button once. On your site I can get
in over a dozen clicks before the page comes back to alert me. This also
means I posted 10 requests to your server instead of just one. If you were
doing a database app that required a few seconds to process and has multiple
steps it will really get hammered and you'll need to rollback 9 transactions
that may have started before the first transaction completed. While you
should have the logic to rollback those transactions in your app it is best
to do what you can to make sure you only need to executed a minimum number
of times. Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight
If you sign up under me and need help, email me.

"Bishoy George" <bi****@bishoy. com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I tried the code submitted by Ken Dopierala Jr.
It disable the button for a second then when the page is refreshed due to
post back, it is enabled again.

Also the code of Sreejith Ram is not working.

Bishoy
http://bishoy.com
-----------------------------------------------------

"Barry Gilmore" <no**********@y ahoo.com> wrote in message
news:ro******** ******@tornado. rdc-kc.rr.com...

Is there a way to disable a button after it is clicked?

I am trying to avoid having someone click on it twice while they wait for it to process.

Thank you!

[Bishoy George]

Hi Ken,
Your opinion is very reasonable.

But, I want an extra code to prevent the disabled button by adding
attributed from become active again.

Thanks.
Bishoy

------------------------------------------------------------------------

"Ken Dopierala Jr." <kd*********@wi .rr.com> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..

Hi Bishoy,

That is what it is supposed to do. Let's say you are doing a credit card
payment. It makes sure the user can only click once. Then after
processing
is done they are redirected to a success or failure page. It also lets
the
user know that they can only click the button once. On your site I can
get
in over a dozen clicks before the page comes back to alert me. This also
means I posted 10 requests to your server instead of just one. If you
were
doing a database app that required a few seconds to process and has
multiple
steps it will really get hammered and you'll need to rollback 9
transactions
that may have started before the first transaction completed. While you
should have the logic to rollback those transactions in your app it is
best
to do what you can to make sure you only need to executed a minimum number
of times. Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight
If you sign up under me and need help, email me.

"Bishoy George" <bi****@bishoy. com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I tried the code submitted by Ken Dopierala Jr.
It disable the button for a second then when the page is refreshed due to
post back, it is enabled again.

Also the code of Sreejith Ram is not working.

Bishoy
http://bishoy.com
-----------------------------------------------------

"Barry Gilmore" <no**********@y ahoo.com> wrote in message
news:ro******** ******@tornado. rdc-kc.rr.com...

> Is there a way to disable a button after it is clicked?
>
> I am trying to avoid having someone click on it twice while they wait for > it to process.
>
> Thank you!
>
>

[Sreejith Ram]

Well Bishoy, I think the issue we trying to address is , if the user click
multiple times on submit button, the client browser would send multiple post
requests to the web server. This happens a lot when the client connection is
slow. Our code doesnt have any control on this because the browser would
think these are 2 diffrent posts by the user.

The simplest solution for it is to stop the user from clicking multiple
times by disabling the button at clientside after the first click. .so that
multiple requests are not send to the server by the browser. Like Justin
Gengo pointed this wouldnt work if you have validators though ..

Once you are at the Server Side OnClick event, you would be able to take the
additional step of disabling the button , clearing form data, redirecting the
page etc etc depending on the requirement of your app. But if you disable the
submit button for good, how will the user make the next submit?

"Bishoy George" wrote:

Hi Ken,
Your opinion is very reasonable.

But, I want an extra code to prevent the disabled button by adding
attributed from become active again.

Thanks.
Bishoy

------------------------------------------------------------------------

"Ken Dopierala Jr." <kd*********@wi .rr.com> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..

Hi Bishoy,

That is what it is supposed to do. Let's say you are doing a credit card
payment. It makes sure the user can only click once. Then after
processing
is done they are redirected to a success or failure page. It also lets
the
user know that they can only click the button once. On your site I can
get
in over a dozen clicks before the page comes back to alert me. This also
means I posted 10 requests to your server instead of just one. If you
were
doing a database app that required a few seconds to process and has
multiple
steps it will really get hammered and you'll need to rollback 9
transactions
that may have started before the first transaction completed. While you
should have the logic to rollback those transactions in your app it is
best
to do what you can to make sure you only need to executed a minimum number
of times. Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight
If you sign up under me and need help, email me.

"Bishoy George" <bi****@bishoy. com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

I tried the code submitted by Ken Dopierala Jr.
It disable the button for a second then when the page is refreshed due to
post back, it is enabled again.

Also the code of Sreejith Ram is not working.

Bishoy
http://bishoy.com
-----------------------------------------------------

"Barry Gilmore" <no**********@y ahoo.com> wrote in message
news:ro******** ******@tornado. rdc-kc.rr.com...
> Is there a way to disable a button after it is clicked?
>
> I am trying to avoid having someone click on it twice while they wait

for

> it to process.
>
> Thank you!
>
>

[JIMCO Software]

Sreejith Ram wrote:

The simplest solution for it is to stop the user from clicking
multiple times by disabling the button at clientside after the first
click. .so that multiple requests are not send to the server by the
browser. Like Justin Gengo pointed this wouldnt work if you have
validators though ..

The following will work even if you have validation controls:

System.Text.Str ingBuilder sb = new StringBuilder() ;
sb.Append("if (typeof(Page_Cl ientValidate) == 'function') { ");
sb.Append("if (Page_ClientVal idate() == false) { return false; }} ");
sb.Append("this .value = 'Please wait...';");
sb.Append("this .disabled = true;");
sb.Append(Page. GetPostBackEven tReference(btnS ubmit));
sb.Append(";");
btnSubmit.Attri butes.Add("oncl ick", sb.ToString());

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

[Sreejith Ram]

thanks

"JIMCO Software" wrote:

Sreejith Ram wrote:

The simplest solution for it is to stop the user from clicking
multiple times by disabling the button at clientside after the first
click. .so that multiple requests are not send to the server by the
browser. Like Justin Gengo pointed this wouldnt work if you have
validators though ..

The following will work even if you have validation controls:

System.Text.Str ingBuilder sb = new StringBuilder() ;
sb.Append("if (typeof(Page_Cl ientValidate) == 'function') { ");
sb.Append("if (Page_ClientVal idate() == false) { return false; }} ");
sb.Append("this .value = 'Please wait...';");
sb.Append("this .disabled = true;");
sb.Append(Page. GetPostBackEven tReference(btnS ubmit));
sb.Append(";");
btnSubmit.Attri butes.Add("oncl ick", sb.ToString());

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

[S. Justin Gengo]

Jimco,

Yes, that's what my disable submit function (submitted above) does.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"JIMCO Software" <co*******@jimc osoftware.com> wrote in message
news:u4******** ********@tk2msf tngp13.phx.gbl. ..

Sreejith Ram wrote:

The simplest solution for it is to stop the user from clicking
multiple times by disabling the button at clientside after the first
click. .so that multiple requests are not send to the server by the
browser. Like Justin Gengo pointed this wouldnt work if you have
validators though ..

The following will work even if you have validation controls:

System.Text.Str ingBuilder sb = new StringBuilder() ;
sb.Append("if (typeof(Page_Cl ientValidate) == 'function') { ");
sb.Append("if (Page_ClientVal idate() == false) { return false; }} ");
sb.Append("this .value = 'Please wait...';");
sb.Append("this .disabled = true;");
sb.Append(Page. GetPostBackEven tReference(btnS ubmit));
sb.Append(";");
btnSubmit.Attri butes.Add("oncl ick", sb.ToString());

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

[JIMCO Software]

S. Justin Gengo wrote:

Jimco,

Yes, that's what my disable submit function (submitted above) does.

Sorry if reposted. I posted in response to a "doesn't work with validators"
post. I hide read posts, do unless I happen to remember a previous post's
content, it's gone clear into another realm by the time I might respond. ;)

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com