OH sure, so they can't click. PERFECT!
----- Original Message -----
From: [email protected]
To: RBASE-L Mailing List
Sent: Wednesday, February 24, 2010 3:07 PM
Subject: [RBASE-L] - Re: Browse to Edit in a form
Ooops, just found a gotcha that I'm going to report to the
developers site. If you have combo boxes on your form, you can
drop down, pick an item, see it reflected in your field, leading you
to believe you just made a change. If you tab to another field you
will see that your value goes back to the original value. So it does
NOT save, but it could be confusing to the user. If you don't go to
another field and rather just exit the form, you would probably think
your change got saved.
I fixed this by giving all my combo boxes a componentid of "combo"
and added:
PROPERTY combo ENABLED FALSE
to my on after start eep, and set it to TRUE in my edit button.
Karen
that is cool!!
(oh I hope I get another RBase project to do one day!!)
----- Original Message -----
From: [email protected]
To: RBASE-L Mailing List
Sent: Wednesday, February 24, 2010 2:40 PM
Subject: [RBASE-L] - Re: Browse to Edit in a form
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
