Hello A5 fans,
If anyone can assist it will be greatly appreciated:
BACKGROUND:
Have a fairly simple form used to add records only, no changes allowed. When a key field is filled in via a lookup, a subform is opened as read-only, to display some
meaningful info from another table. Everything works well,
even a check for duplicate key, however.....
PROBLEM DESCRIPTION:
I had a nice routine for the ONKEY event of the parentform
to trap the ESC key, so I could cleanly take care of the form, and present a blank record again for add mode. Seems ONKEY FLAKES out when the subform is used, that is, I copied the parentform to another name, deleted the subform, and PRESTO, the ONKEY logic works. But I can't seem to get
it to work while the subform exists.
WORKAROUND, SORT-OF:
I do have a work around where a 'CANCEL' button will do the
same sort of 'clean-up-the-form' logic as in the ONKEY script. However, this is not desired as the user can see
the mess that A5 leaves behind when you let A5 handle the
ESCAPE key, until the user can press the 'CANCEL' button to
get rid of the mess.
A5 COMPLAINT:
You see the ESCAPE key has to be allowed to work first, as
a typical cancel operation is when a user tries to enter
a record that already exists, "duplicate key situation",
only ESCAPE can stop the "duplicate key situatioon", CANCEL
button won't do it. But again, when you let A5 do the ESCAPE key, it clears the condition ok, but then fills the form with unwanted data from record 1 of the table. Don't want to see that record, or any other when I'm in add mode, thank you very much.
Any replies will be very much appreciated.
Later
If anyone can assist it will be greatly appreciated:
BACKGROUND:
Have a fairly simple form used to add records only, no changes allowed. When a key field is filled in via a lookup, a subform is opened as read-only, to display some
meaningful info from another table. Everything works well,
even a check for duplicate key, however.....
PROBLEM DESCRIPTION:
I had a nice routine for the ONKEY event of the parentform
to trap the ESC key, so I could cleanly take care of the form, and present a blank record again for add mode. Seems ONKEY FLAKES out when the subform is used, that is, I copied the parentform to another name, deleted the subform, and PRESTO, the ONKEY logic works. But I can't seem to get
it to work while the subform exists.
WORKAROUND, SORT-OF:
I do have a work around where a 'CANCEL' button will do the
same sort of 'clean-up-the-form' logic as in the ONKEY script. However, this is not desired as the user can see
the mess that A5 leaves behind when you let A5 handle the
ESCAPE key, until the user can press the 'CANCEL' button to
get rid of the mess.
A5 COMPLAINT:
You see the ESCAPE key has to be allowed to work first, as
a typical cancel operation is when a user tries to enter
a record that already exists, "duplicate key situation",
only ESCAPE can stop the "duplicate key situatioon", CANCEL
button won't do it. But again, when you let A5 do the ESCAPE key, it clears the condition ok, but then fills the form with unwanted data from record 1 of the table. Don't want to see that record, or any other when I'm in add mode, thank you very much.
Any replies will be very much appreciated.
Later
Comment