Hi Mike,
I have used variables with the same background color as the form so they
only show up when they are not null. In other words, as long as the variable
is null nothing is seen. When something occurs that needs to notify the user
then I set the variable (in the EEP) and recalc variables. It is not a check box
but may be a suitable solution. Version 7 will probably have the capacity to
do exactly what you are asking (and so much more!). To answer your
question- Files run by push buttons are EEPs.
If you really need to exit the form and then reenter it then I would suggest
setting a variable in the EEP and then use the CLOSEWINDOW command
in the EEP to exit the form which will return you to the code that originally
called the form. Based on the variable that you set in the EEP, you could
have code there that will take the user back into the form. I have not tried
this but in theory it should work.
Best regards,
Mike Young
On Mon, 28 May 2001 15:58:30 -0400, Michael Sinclair wrote:
>Hi all,
>
>I've got a form with a bunch of push buttons on it. Each push button
>runs a small file that
>adds, modifies, or deletes rows from a different table. I want to be
>able to display some
>kind of indication on the form (that would change) depending on what the
>user did after pushing
>the push button. For example, if the user deleted all of the rows in
>the table, then a check box
>could be unchecked. If the user left any rows at all in the table, then
>a check box could be
>checked. Now here is the problem.....the check box won't change until
>after I have exited and
>reenterd the form. But I can't do that from within the code activated
>by the push button---some
>evil error message says that is illegal from within an EEP (are files
>run by push buttons considered
>EEPs?). But I also can't use SCREEN RESTORE OFF, cuz that only
works
>within EEPs. ARGH!
>
>The only way I found to make it work is to have the push button command
>file end with
>EDIT USING formname.....but it get's ugly when you try to leave (all the
>previous uses of the
>form are still open, albeit hidden) and they each have to get
>closed....and eats memory).
>
>So.......how do smart Rbase users do this? AND does this have anything
>to do with SET FOCUS,
>or MDI (can anybody give me an example of how and when to use SET
FOCUS
>and MDI??)
>
>TIA!
>
>Mike Sinclair
>
