On Thu, 27 May 2004 11:46:04 -0700, "Rich"
<an*******@discussions.microsoft.com> wrote:
It wouldn't be in a session variable unless you wrote code that stored it in a session variable (which would have to have been before the control was rendered to the client.)
The easiest thing would probably be to make it a Web Control, something like this:
<asp:TextBox id="pwtext" style="Z-INDEX: 103; LEFT: 141px; POSITION: absolute; TOP: 27px" runat="server" TextMode="Password"></asp:TextBox>
When your form is submitted back to the server, the value will be accessible in code-behind like this: TextBox1.Text
If, for some reason, you don't want to use a Web Control, the text box value will be avaiable to your server-side application if it was included in a submitted form. Assuing METHOD=POST, you would be able to access it with the following expression: Request.Form.Item("pwtext"))
Thanks, Request.Form.Item("pwtext")) does it.
I didn't even notice that the asp textbox had a password textmode or I
likely would have used it. But, I thought the general idea was to use
HTML controls wherever the extra overhead of server controls wasn't
needed. In this case I don't want it to maintain state and I don't
need to refer to it except to get the value. So is there a reason to
make it a server control?
