Tracy - tx for the reply Tracy Pearson wrote: > If ShowData isn't a public variable, and this is happening in a method, > it's only private until that method goes away. > I think that you and Ed have pinpointed what is in effect a scoping problem > You could bindevent to a public object, which you can raise when > wexist(). The boundevent would call a method on the child form to > reload, and bring it back to the front. > I'm not sure that I understand that - I'll sleep on it ... > Or if wexist() you could activate window "ShowData". Now to get it to > reload, you'll need _Screen.ActiveForm.methodtoreload() > I need to think this through again because although the ACTIVATE WINDOW approach would work I don't think I really want to do that - I just want to refresh what is displayed in the child window whilst keeping focus in the parent form. But it's certainly an approach I'll look at tomorrow. > Or if wexist() you could loop _screen.forms until you find the one that > you want to bring back, call the method and bring it back to the foreground. > That brings us back to square one - I've found the one I want , now I need to be able to call one of its methods from the parent form ... Anyway , plenty of food for thought and things to try tomorrow
Paul Newton _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
