Combining WaitWindowClosed and Dialog Boxes?

[dbish]

I have a script that goes to multiple locations on the Internet and harvests data. Often, the websites will be non-responsive so the script will stop and report the error. I will try it later and tell it to pickup whereever it left off. To do this, I created a dialog box with 4 possible locations to begin running the script. This dialog box loads as soon as script runs and requires user action. All this works great when I am around to push the button.

Now, I want to schedule the script to run in the middle of the night. What I am looking for is some way to Wait 60 seconds for user input and, if none is coming, start the beginning of the processing. Something like a WaitWindowClosed mechanism whereby a result code is generated that Msched can see and know to close dialog box and process the script.

I know that I could make a copy of the script for unattended usage without the dialog box but would like to try the WWC approach first since the script changes over time and I don't want to have to remember to fix both versions.

Any suggestions?

Dave

[Bob Hansen]

I agree with this idea. I submitted this as a request last April, and added a Poll in June.

Perhaps you can cast a vote at:
http://www.mjtnet.com/usergroup/viewtop ... nt+request

I am not sure that my idea of WW_TIMEOUT actually works on the Dialog box. I never actually tried it, but it sounded good in theory. The If>Result= option would not work unless the window timed out. that is the basic problem.

[dbish]

Bob,

Thanks for the reply. I tried the two workarounds in your old post- neither worked. I think an improvement to MSched is the only way around this (of course I may have not tried the workarounds in all forms possible - I did try many different sequences without luck).

Voted in yoir poll - Hope Marcus catches this thread.

Dave