Thanks guys for the input.
The statistics method calls the form refresh already. I was confident that DOEVENTS would solve the problem but including one before calling and one every other line inside the method had no apparent effect.
I have not tried the timer - it seems like overkill but I did try a wait window before calling the statistics method. For some reason the wait window did not seem to show up.
I just now caught what is happening - the wait window comes up at the same time the secondary form comes up. That means the code after calling the form executes right away so I expect the solution is stop execution until the secondary form is exited. How do I do that?
Joe
On Tue, Feb 23, 2016 at 12:00 PM, Dave Crozier DaveC@flexipol.co.uk wrote:
Joe, Also sprinkle a number of Doevents around in your statistics method so that windows has enough time to regenerate the refresh loop.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Joe Yoder Sent: 23 February 2016 16:31 To: profoxtech@leafe.com Subject: Controling the order/timing of processing after doing a form
The click method of a command button on my main form has the following code: DO FORM DrillDown.scx THISFORM.statistics
The secondary form updates data in a table. The statistics method calculates statistics on the table and updates the screen
When the main form command button calls the code above, the screen is not updated immediately. Another Debug button that calls the statistics method updates the screen properly.
What do I need to add so that the screen gets updated properly?
Thanks in advance,
Joe
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]