This too. I revert to building forms with HTML boxes when the form is not editable. This can be a PITA if/when you change the name of fields.Jaymer wrote:Along with this, it irks me that I can't [easily] have a button on the screen in DISABLED status.craigd wrote: 6. Form attributes that are READ ONLY (eg if PROTECT rule is true) should actually LOOK like they are read only. Today they look like READ/WRITE attributes except when you click on them - to edit them - nothing happens. My 'trick' is to add the READ only attributes inside an HTML box so at least they look READ only.
... like until this BO has x, y & z entered and validated, THEN a particular button changes state from disabled to enabled (ie. not just appearing out of nowhere due to a READ PROTECT).
And also, using a VIEW still makes the field look like an editable field, even tho you are in VIEW mode (the user doesn't know this).
Though the VIEW command is not and uneditable state, you have to add NOEDIT to make it non editable. (See Note at p369 User Guide)