T
Terry Holland
I have an asp page that contains a user control. This control is a panel
containing a number of link buttons that get displayed if certain conditions
in the db are met and these conditions can take quite a while to evaluate.
Consequently that page can take a while to open. These links are alert for
users indicating that they need to perform some actions. If they click any
of the links they will get redirected to the appropriate page.
Unfortunately, the action of clickin the link causes a postback which in
turn build the control which in turn checks the conditions which is a slow
process... All of this when all the user really wants to do is navigate to
a new page. Is there any way of avoiding all of this processing and just
drop straight into the event that caused the postback?
I have tried checking the IsPostback property on the Page_Load event and not
building the control if it is, but this does not work as there are no link
buttons to respond to!!
I have the same problem in other areas of the application where I have other
dynamically created controls (mainly datagrids). These grids generally have
a column containing an Edit button which, when clicked, causes a postback,
rebuilds the grid and populates the grid before it is able to detect which
rows Edit button was clicked and then redirect to another page. Again, if I
dont recreate the grid and populate at runtime, nothing happens in terms of
redirecting to required page.
Help appreciated
Terry Holland
containing a number of link buttons that get displayed if certain conditions
in the db are met and these conditions can take quite a while to evaluate.
Consequently that page can take a while to open. These links are alert for
users indicating that they need to perform some actions. If they click any
of the links they will get redirected to the appropriate page.
Unfortunately, the action of clickin the link causes a postback which in
turn build the control which in turn checks the conditions which is a slow
process... All of this when all the user really wants to do is navigate to
a new page. Is there any way of avoiding all of this processing and just
drop straight into the event that caused the postback?
I have tried checking the IsPostback property on the Page_Load event and not
building the control if it is, but this does not work as there are no link
buttons to respond to!!
I have the same problem in other areas of the application where I have other
dynamically created controls (mainly datagrids). These grids generally have
a column containing an Edit button which, when clicked, causes a postback,
rebuilds the grid and populates the grid before it is able to detect which
rows Edit button was clicked and then redirect to another page. Again, if I
dont recreate the grid and populate at runtime, nothing happens in terms of
redirecting to required page.
Help appreciated
Terry Holland