Hi:
I have a sequence of calls to forms and database.load commands that depending on where I place the HideProgress command either keeps the Progress dialog on the screen, or removes it incorrectly along the way.

The documentation says 'if the  reference count is 0, hides the  active progress dialog'. How can I set the global progress reference count := 0 before I issue the HideProgress.

<< I have a sequence of calls to forms and database.load commands that depending on where I place the HideProgress command either keeps the Progress dialog on the screen, or removes it incorrectly along the way. >>

If you're getting a mismatch, then you're most likely not issuing the ShowProgress/HideProgress calls correctly.  Please send me an example project that demonstrates what you're seeing, and I'll tell you what the issue is.

Tim Young
Elevate Software
www.elevatesoft.com

<< If you're getting a mismatch, then you're most likely not issuing the ShowProgress/HideProgress calls correctly.  Please send me an example project that demonstrates what you're seeing, and I'll tell you what the issue is. >>

Tim:
It works properly in the normal sequence so I can't quickly do a sample project.

I am automating the actions to land users on forms within panels and other forms etc. Because of this, the Progress window was disappearing completely and reappearing after a second or two.

So, where I would normally have a HideProgress, I don't want and I have it show another ShowProgress with new 'Loading....' text.

There are a whole lot of conditions that would determine if to HideProgress now or not, so I was hoping that by setting the global progress reference count to '0' would ensure that all progress dialogs used along the way are e cleared.

<< There are a whole lot of conditions that would determine if to HideProgress now or not, so I was hoping that by setting the global progress reference count to '0' would ensure that all progress dialogs used along the way are e cleared. >>

So, you're saying that you're not sure if you're matching HideProgress calls properly with ShowProgress calls ?

Tim Young
Elevate Software
www.elevatesoft.com

<< So, you're saying that you're not sure if you're matching HideProgress calls properly with ShowProgress calls ?>>

I just encountered this issue again. As a rule, I now issue a HideProgress before every ShowProgress.

<< I just encountered this issue again. As a rule, I now issue a HideProgress before every ShowProgress. >>

The only way to encounter this issue is to have a mismatch between the number of ShowProgress/HideProgress calls.  Browser UIs are single-threaded, so there's no way to have the reference counts get out of whack unless there's an issue with the number of calls of each respective procedure.

Tim Young
Elevate Software
www.elevatesoft.com