Re: Witango-Talk: Disabling form fields

[Dale Graham]

What we do is something like this (let's presume text fields for this example) Based on access levels/function Accessible field: <text input box> Inaccessible field:  data string             <hidden text field with data in it> Works like a charm I am not sure, however, that this addresses what you are attempting to achieve. However, hidden fields can work very well when you're attempting such updates and don't want to lose data in the process. On Jul 12, 2005, at 7:57 PM, Chuck Lockwood wrote: What is the easiest, safest, most reliable way to disable editing of selected form fields based on privilege levels or other criteria.   I have used in the past, but was hoping to use disabled=true now.  I find it displays the fields grayed out which is great, but doesn’t include them as arguments, which is not good.   What other solutions are there for always displaying the data but restricting edits on various fields without messing up the existing update action? Chuck Lockwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LockData Technologies, Inc.                  309 Main Avenue, Hawley, Pa 18428          570-226-7340 ~ Fax: 570-226-7341    [EMAIL PROTECTED] ~ www.lockdata.com                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf