Simon,
You may not want to put your passwords into a hidden text field simply
because it is in plain text if someone does "View Source" on the page
(perhaps not an issue).
Might I suggest a few other possibilities:
(1) Rearchitect the "roles" handling so it doesn't require a postback
(don't know what you code is doing, so I can't tell if this is
feasible).
(2) Make the password change and the "roles" handling separate
processes on two different pages.
(3) Make the user save the password changes before performing the
"roles" processing. After the postback, the password fields would be
blank, but they would already be saved. Not the nicest UI
implementation, but there it is.
Good luck.
-- Paul
"Simon Harvey" <si**********@the-web-works.co.uk> wrote in message news:<Og**************@TK2MSFTNGP11.phx.gbl>...
The reason why I have to do this is that I have a form that allows the
system admin of a website to create a new user for the site.
He needs to put in various details including an initial password for the
user. The user changes this at first login.
Also on the page are two list boxes, the first containing all available
roles, and the other containing any roles that you want to assign to the new
user. When you click to add a role to the user, the postback occurs.
Any thoughts would be great. Thanks for your help
Simon