Postbacks confusing to the user - any suggestions???

[Glenn]

Hi!

I've developed an app that displays multiple textbox and
combobox fields (most of which are autopostback) on a form
along with a submit button. My users find it confusing
when they change data in one of the autopostback textboxes
then click on the 'submit' button and, instead of seeing
the next form they see the same form come back to them, as
if they never clicked the 'submit' button. What's
happening behind the scenes is that changing the text box
then clicking the 'submit' button first triggers
the 'onblur' event of the textbox which triggers the
postback, so the click of the 'submit' never really
happens to the backend. Does anyone have any suggestions
on what my options are to make this clearer to the end
user (I do have a 'Please wait' message during postback
but that doesn't clarify things - it's the same form
coming back that doesn't make sense to them, all they know
is that they pressed 'submit'). Is there any clever way
for the back end (vb.net/asp.net) code to detect that the
submit has been clicked so that I can consolidate the 2
operations?

Thanks in advance,

Glenn

[George Ter-Saakov]

Do not show the Submit button until ready.

George.

"Glenn" <gl**@instec-corp.com> wrote in message
news:18******** *************** *****@phx.gbl.. .

Hi!

I've developed an app that displays multiple textbox and
combobox fields (most of which are autopostback) on a form
along with a submit button. My users find it confusing
when they change data in one of the autopostback textboxes
then click on the 'submit' button and, instead of seeing
the next form they see the same form come back to them, as
if they never clicked the 'submit' button. What's
happening behind the scenes is that changing the text box
then clicking the 'submit' button first triggers
the 'onblur' event of the textbox which triggers the
postback, so the click of the 'submit' never really
happens to the backend. Does anyone have any suggestions
on what my options are to make this clearer to the end
user (I do have a 'Please wait' message during postback
but that doesn't clarify things - it's the same form
coming back that doesn't make sense to them, all they know
is that they pressed 'submit'). Is there any clever way
for the back end (vb.net/asp.net) code to detect that the
submit has been clicked so that I can consolidate the 2
operations?

Thanks in advance,

Glenn

[Rasika Wijayaratne]

I am not too sure that I understand your problem very clearly, but I'll try to help anyway based on my understanding of your situation. Becasue the button can have its own event handler (e.g. Button1_Click), you can put whatever code/functionality in here to differentiate from an AutoPostBack. To create an event handler for the button, double click on it in Design View and Visual Studio will create one for you

To actually differentiate between an AutoPostBack and a Button_Click: When the Button_Click occurs you can hide all the WebControls and display a "Thank you for your submission" message. One way of achieving this is by using two Panel controls. Panel1 would contain all the WebControls, and Panel2 can contain the message. Intiially Panel1 is visible and Panel2 is hidden. When the Button_Click occurs, hide Panel1 and show Panel2

Rasika Wijayaratne