By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,077 Members | 1,790 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,077 IT Pros & Developers. It's quick & easy.

Find out the control that initiated the postback event

P: n/a
Dan
Hi,

I'd like to find out the control that caused a postback to be raised. Obviously this could simply done in a control event handler. I am not going to do this method and would like no references as to how to do it this way as I already know how.

I know this may be getting into advanced or unheard of territory.

I have some custom web user controls that are dynamically created at run time along with other controls. I can still add an event handler to these controls, but unfortunately the event handler wont fire until the controls are re-created on the postback, but I don't want the start-up code running on a post back, I need it to run in the event of the control that cuased the post back. This works fine for my other controls on the form that arn't generated, but will not for this user control, so I need an alternative.

I need some indication in my page_load (or init) event that tells me that our user control has initiated the postback and to then run start up code.

Are there any techniques out there that allow me to dig into the postback and discover what control or control type made the postback?

Another solution I could add a client side handler that could set the value of a checkbox but due to the complexity of the user control I am not going to do that, as a post back could be initiated by a multiple number of events on different controls within the user control.

Thats my question! Thanks..
Nov 18 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
You should be able to add an eventhandler, but if you don't want to you can use Request.Form("__EVENTTARGET"). You must have a control on your form that renders the function __doPostBack(eventTarget, eventArgument) on your page. Many controls will put the function on your page. You could always put a dummy control like a linkbutton or something on your page to force the script to be rendered. Hope this helps.

"Dan" <no********@nowhere.com> wrote in message news:%2****************@TK2MSFTNGP10.phx.gbl...
Hi,

I'd like to find out the control that caused a postback to be raised. Obviously this could simply done in a control event handler. I am not going to do this method and would like no references as to how to do it this way as I already know how.

I know this may be getting into advanced or unheard of territory.

I have some custom web user controls that are dynamically created at run time along with other controls. I can still add an event handler to these controls, but unfortunately the event handler wont fire until the controls are re-created on the postback, but I don't want the start-up code running on a post back, I need it to run in the event of the control that cuased the post back. This works fine for my other controls on the form that arn't generated, but will not for this user control, so I need an alternative.

I need some indication in my page_load (or init) event that tells me that our user control has initiated the postback and to then run start up code.

Are there any techniques out there that allow me to dig into the postback and discover what control or control type made the postback?

Another solution I could add a client side handler that could set the value of a checkbox but due to the complexity of the user control I am not going to do that, as a post back could be initiated by a multiple number of events on different controls within the user control.

Thats my question! Thanks..
Nov 18 '05 #2

P: n/a
Dan
the items do actually exist in the Request.Form collection...

but are ""
"vMike" <Mi************@gewarren.com.nospam> wrote in message news:bq**********@ngspool-d02.news.aol.com...
You should be able to add an eventhandler, but if you don't want to you can use Request.Form("__EVENTTARGET"). You must have a control on your form that renders the function __doPostBack(eventTarget, eventArgument) on your page. Many controls will put the function on your page. You could always put a dummy control like a linkbutton or something on your page to force the script to be rendered. Hope this helps.

"Dan" <no********@nowhere.com> wrote in message news:%2****************@TK2MSFTNGP10.phx.gbl...
Hi,

I'd like to find out the control that caused a postback to be raised. Obviously this could simply done in a control event handler. I am not going to do this method and would like no references as to how to do it this way as I already know how.

I know this may be getting into advanced or unheard of territory.

I have some custom web user controls that are dynamically created at run time along with other controls. I can still add an event handler to these controls, but unfortunately the event handler wont fire until the controls are re-created on the postback, but I don't want the start-up code running on a post back, I need it to run in the event of the control that cuased the post back. This works fine for my other controls on the form that arn't generated, but will not for this user control, so I need an alternative.

I need some indication in my page_load (or init) event that tells me that our user control has initiated the postback and to then run start up code.

Are there any techniques out there that allow me to dig into the postback and discover what control or control type made the postback?

Another solution I could add a client side handler that could set the value of a checkbox but due to the complexity of the user control I am not going to do that, as a post back could be initiated by a multiple number of events on different controls within the user control.

Thats my question! Thanks..
Nov 18 '05 #3

P: n/a
Dan
Thanks for the reply,

although sounds nice in theory.

I tried it and in every instance of a post back

Diagnostics.Debug.WriteLine(Request.Form("__EVENTT ARGET"))

Diagnostics.Debug.WriteLine(Request.Form("__EVENTA RGUMENT"))

both return a blank string..

Any ideas ?

"vMike" <Mi************@gewarren.com.nospam> wrote in message news:bq**********@ngspool-d02.news.aol.com...
You should be able to add an eventhandler, but if you don't want to you can use Request.Form("__EVENTTARGET"). You must have a control on your form that renders the function __doPostBack(eventTarget, eventArgument) on your page. Many controls will put the function on your page. You could always put a dummy control like a linkbutton or something on your page to force the script to be rendered. Hope this helps.

"Dan" <no********@nowhere.com> wrote in message news:%2****************@TK2MSFTNGP10.phx.gbl...
Hi,

I'd like to find out the control that caused a postback to be raised. Obviously this could simply done in a control event handler. I am not going to do this method and would like no references as to how to do it this way as I already know how.

I know this may be getting into advanced or unheard of territory.

I have some custom web user controls that are dynamically created at run time along with other controls. I can still add an event handler to these controls, but unfortunately the event handler wont fire until the controls are re-created on the postback, but I don't want the start-up code running on a post back, I need it to run in the event of the control that cuased the post back. This works fine for my other controls on the form that arn't generated, but will not for this user control, so I need an alternative.

I need some indication in my page_load (or init) event that tells me that our user control has initiated the postback and to then run start up code.

Are there any techniques out there that allow me to dig into the postback and discover what control or control type made the postback?

Another solution I could add a client side handler that could set the value of a checkbox but due to the complexity of the user control I am not going to do that, as a post back could be initiated by a multiple number of events on different controls within the user control.

Thats my question! Thanks..
Nov 18 '05 #4

P: n/a
Are the control(s) within the form tags?
"Dan" <no********@nowhere.com> wrote in message news:%2***************@tk2msftngp13.phx.gbl...
the items do actually exist in the Request.Form collection...

but are ""
"vMike" <Mi************@gewarren.com.nospam> wrote in message news:bq**********@ngspool-d02.news.aol.com...
You should be able to add an eventhandler, but if you don't want to you can use Request.Form("__EVENTTARGET"). You must have a control on your form that renders the function __doPostBack(eventTarget, eventArgument) on your page. Many controls will put the function on your page. You could always put a dummy control like a linkbutton or something on your page to force the script to be rendered. Hope this helps.

"Dan" <no********@nowhere.com> wrote in message news:%2****************@TK2MSFTNGP10.phx.gbl...
Hi,

I'd like to find out the control that caused a postback to be raised. Obviously this could simply done in a control event handler. I am not going to do this method and would like no references as to how to do it this way as I already know how.

I know this may be getting into advanced or unheard of territory.

I have some custom web user controls that are dynamically created at run time along with other controls. I can still add an event handler to these controls, but unfortunately the event handler wont fire until the controls are re-created on the postback, but I don't want the start-up code running on a post back, I need it to run in the event of the control that cuased the post back. This works fine for my other controls on the form that arn't generated, but will not for this user control, so I need an alternative.

I need some indication in my page_load (or init) event that tells me that our user control has initiated the postback and to then run start up code.

Are there any techniques out there that allow me to dig into the postback and discover what control or control type made the postback?

Another solution I could add a client side handler that could set the value of a checkbox but due to the complexity of the user control I am not going to do that, as a post back could be initiated by a multiple number of events on different controls within the user control.

Thats my question! Thanks..
Nov 18 '05 #5

P: n/a
then the postback was caused by a submit button (or image button). these postback by sending their name and value in form fields collection.

-- bruce (sqlwork.com)

"Dan" <no********@nowhere.com> wrote in message news:#x*************@tk2msftngp13.phx.gbl...
the items do actually exist in the Request.Form collection...

but are ""
"vMike" <Mi************@gewarren.com.nospam> wrote in message news:bq**********@ngspool-d02.news.aol.com...
You should be able to add an eventhandler, but if you don't want to you can use Request.Form("__EVENTTARGET"). You must have a control on your form that renders the function __doPostBack(eventTarget, eventArgument) on your page. Many controls will put the function on your page. You could always put a dummy control like a linkbutton or something on your page to force the script to be rendered. Hope this helps.

"Dan" <no********@nowhere.com> wrote in message news:%2****************@TK2MSFTNGP10.phx.gbl...
Hi,

I'd like to find out the control that caused a postback to be raised. Obviously this could simply done in a control event handler. I am not going to do this method and would like no references as to how to do it this way as I already know how.

I know this may be getting into advanced or unheard of territory.

I have some custom web user controls that are dynamically created at run time along with other controls. I can still add an event handler to these controls, but unfortunately the event handler wont fire until the controls are re-created on the postback, but I don't want the start-up code running on a post back, I need it to run in the event of the control that cuased the post back. This works fine for my other controls on the form that arn't generated, but will not for this user control, so I need an alternative.

I need some indication in my page_load (or init) event that tells me that our user control has initiated the postback and to then run start up code.

Are there any techniques out there that allow me to dig into the postback and discover what control or control type made the postback?

Another solution I could add a client side handler that could set the value of a checkbox but due to the complexity of the user control I am not going to do that, as a post back could be initiated by a multiple number of events on different controls within the user control.

Thats my question! Thanks..
Nov 18 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.