Thank you Dawn! (and others who responded too!),
That was all I was missing! I hadn't thought about the obvious fact that
my Form 1button could issue additional commands. I'm sure that early in
the learning curve, many people go through the same process I'm going
through right now, which is: I ask a question, and seemingly without
fail, the answer I receive immediately seems blatantly obvious!
Alex
Dawn Hast wrote:
Alex,
I think your missing the overall message....
How are you opening Form 2? Since you say you're not using MDI forms,
then the assumption is that Form 2 is being opened from Form 1 - what
object on Form 1 is opening Form 2? For example, if you have a button
on Form 1 that opens Form 2, it probably has an eep that looks
something like this:
SET VAR varname
EDIT USING form2name
RETURN
You just need to modify that eep to be like this:
SET VAR varname
EDIT USING form2name
PROPERTY <componentid> REFRESHLIST 'TRUE'
RETURN
Whatever eep contains the EDIT USING form2name needs to have the
PROPERTY command after it.
-------------- Original message from Alex Sisk
<[EMAIL PROTECTED]>: --------------
> Karen,
>
> You're absolutely right - I don't need the list refreshed until
I have
> returned to Form 1. My idea was to use the button on Form 2 as the
> refresh "trigger". Is there another way to tell Form 1 that I have
> closed out Form 2? All I need is for the refresh to run anytime
during
> or after the closing of Form 2.
>
> Razzak suggested using MDI forms, but since this is one of the last
> minor tweaks on what is otherwise a working system for one of my
> colleagues, I think I'll learn MDI forms on my next project.
>
> Thanks for your insight!
>
> Alex
>
> [EMAIL PROTECTED] wrote:
> > Alex: Jan's suggestion is in the Form 1 button code that calls
Form
> > 2. You notice that it calls Form 2, and after you exit Form 2 and
> > return back to the button code it will do the property
refreshlist.
> > At that point you are back in Form 1. I'm not sure why you would
> > need to refresh the list in Form 1 while you are sitting in
Form 2.
> > You wouldn't be able to see or do anything with it. So bring
up your
> > form 2. You exit form 2, and then do the refreshlist.
> >
> > Karen
> >
> >
> >> Dan &Jan,
> >>
> >> Thanks for your replies.
> >> This is correct, I am not using MDI forms. The syntax in your
response,
> >> Jan, is what I initially tried. The problem is, I am given a
message
> >> indicating that the component ID that I am referring to is
not within
> >> Form 2 (which is correct). In other words, it is only looking
for a
> >> matching component ID within Form 2, and I cannot seem to
reference Form
> >> 1...
> >>
> >> Alex
> >>
> >> jan johansen wrote:
> >> >Alex,
> >> >
> >> >Dan's suggestion is correct.
> >> >But if you are not using MDI forms the easy suggestion is in
the the
> >> >button
> >> >that calls form2 just do this.
> >> >
> >> >EDIT USING Form2
> >> >PROPERTY form1varlist REFRESHLIST TRUE
> >> >
> >
>
