Re: Need Help for Developing a Form
Date: 1997/10/03
Message-ID: <01bcd022$3f74b590$2aaeb6cc_at_dino>#1/1
Try the when-vaildate-item trigger. Put the logic of enabling or disabling your buttons in there.
Benjamin H. Tay <htay_at_uoft02.utoledo.edu> wrote in article
<01bccfa7$4e671dc0$0a64b783_at_benjamin-tay>...
> Hi,
> I was trying to build a form application with several text boxes, and
> navigation buttons. However, I would like to enhance some security
> integration as follows:
>
> *When I willingly or unwillingly change a data (when I hit the keyboard,
> exclude mouse click to the text box), I would like to disable all the
> navigation buttons (next, previous, first, and last), then CANCEL and
SAVE
> buttons will be active that can force users click one of them...So when I
> click CANCEL will "clear_record" and SAVE will "commit_record".
>
> Can anyone help? In what trigger so I enforce? Any codes provided will
be
> greatly appreciated! Thanks in advance!
>
>
>
> --
> Sincerely,
>
>
> Benjamin Tay
> =======================
> A New RDBMS Learner
> ****************/////000\\\\\
>
Received on Fri Oct 03 1997 - 00:00:00 CEST