Unfortunately, there's no way for the server to initiate the contact with
the client so once page1 has been rendered, anything that happens in page2,
such as a hyperlink click, can't be passed by the server back to page1.
One way in which I have accomplished similar tasks in the past is to use Web
Dialogs. When the user clicks the appropriate "add" button in the web
dialog:
Pass the information to the parent page,
Set hidden form field values in javascript,
Submit the form programmatically,
DataBind the drop-down list again at that time.
In the case of error or failure to add, you can set a client side variable
that is checked on page load and re-open the web dialog again if necessary
when the page loads.
In a fast intranet situation it works very well. On dial-up, auto postback
of any kind sucks!
Dale
"Keith" <Th**********@comcast.net> wrote in message
news:6c**************************@posting.google.c om...
I have this simple scenario.
--------
Choose an item ->dropdownlist-> or <a>Create a new item</a>
--------
When someone decides to click on the create a new item link, it takes
them to a page in which they can enter more records to the database
field to which the dropdownlist is bound.
Then they close this page. And they are again looking at the
dropdownlist. However, I want their newly created data to be present
in the dropdownlist after they close the enter-more-data page.
HOW!!!?!
I'm simply trying to react to a client envet of them closing this
window created by an <asp:HyperLink> link, and then having that event
trigger another DataBind of the dropdownlist on the original page.
Coordinating a client event with a code-behind method is proving
difficult.
Please help.
Thanks,
Keith