The only way you can avoid a postback is if you apply the logic in
Javascript. In other words, it can be done either on the client or on the
server...like most things. If you do it in javascript, you need to worry
about it being cross-browser compatible and perhaps the user won't have
javascript enable. On the server you take the extra performance hit and the
less than perfect UI experience. I can't make that decision for you as it
mostly depends on who your audience is and if you are willing to do both..
Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/
"djc" <no***@nowhere.com> wrote in message
news:Of**************@tk2msftngp13.phx.gbl...
I want to have a form with several fields that first load 'locked' or
read-only. I will have a section on the page that will list several action
options to the user. Each of these actions will simply 'enable' or make
editable certian text box or listbox controls on the same page.
I am assuming I would HAVE to use one of the button controls because a
post back would be necessary. Is this correct? or could I use a hyperlink
control and avoid the post back?
any info is appreciated. Thanks.