M
Mike
Scenario:
1. I dynamically generate a form (using server-side code) with
numerous text boxes that are populated with values from a database.
2. A user enters text all in lower case then clicks save which submits
the page to the server.
3. In the server-side code, I convert the text to all uppercase then
save to a dbf. (Unfortunately I have no control over the database
format and dbf data really needs to be in uppercase because you can't
perform a case-insensitive query on dbf, hence the need for uppercase)
4. I repeat step 1 to redisplay the page and Voila! The page still
displays the value in lower case. BTW, viewstate is set to false.
After pulling my hair out on this one for an insane amount of time, I
came across this article http://support.microsoft.com/?id=316813 which
basically states that what I'm experiencing is by design, which IMHO
totally sucks.
I found a reasonable work-around which is to Response.Redirect to the
same page if IsPostback = True, which forces the page to load from
scratch. But that totally defeats the purpose of this whole ASP.NET
philosophy. So my question is: Am I crazy? Is this really true? Is
there no way to change this behavior? (and while I'm at it, Is Rush
Limbaugh really going to be a regular on Sunday NFL Countdown?)
Someone please tell me there's a better way!!
1. I dynamically generate a form (using server-side code) with
numerous text boxes that are populated with values from a database.
2. A user enters text all in lower case then clicks save which submits
the page to the server.
3. In the server-side code, I convert the text to all uppercase then
save to a dbf. (Unfortunately I have no control over the database
format and dbf data really needs to be in uppercase because you can't
perform a case-insensitive query on dbf, hence the need for uppercase)
4. I repeat step 1 to redisplay the page and Voila! The page still
displays the value in lower case. BTW, viewstate is set to false.
After pulling my hair out on this one for an insane amount of time, I
came across this article http://support.microsoft.com/?id=316813 which
basically states that what I'm experiencing is by design, which IMHO
totally sucks.
I found a reasonable work-around which is to Response.Redirect to the
same page if IsPostback = True, which forces the page to load from
scratch. But that totally defeats the purpose of this whole ASP.NET
philosophy. So my question is: Am I crazy? Is this really true? Is
there no way to change this behavior? (and while I'm at it, Is Rush
Limbaugh really going to be a regular on Sunday NFL Countdown?)
Someone please tell me there's a better way!!