I have this implemented, and it's even smarter than I thought it would be!
My form is already designed with a few controls as being read-only, such as
my primary key fields.
Form "on after start" eep: PROPERTY TABLE pomemos 'READONLY TRUE'
"Edit" button: PROPERTY TABLE pomemos 'READONLY FALSE'
PROPERTY premark SET_FOCUS TRUE
What's really sweet is that any fields you individually marked as read-only
stay read-only even when you press the "edit" button! I thought that
perhaps it would make all the controls read-only so that I would have to then
create component ids for those controls that I would back to read-only, but I
don't have to!
It may be in the future that there will be some fields we want to remain
read-only depending on user security level, but those I will assign a block of
component ids and turn them back to read-only in my "edit" button after
doing the table command.
Karen
