The situation: I have a VFP5 app that triggers the CarbonCopy32 autopilot to send data to client sites. I want Foxpro to sit quietly and wait for CC32 to finish in order to conserve resources, etc.

CarbonCopy has nothing unique as far as I know that complicates this; I'm just missing something. For comic effect if nothing else, here are:

Old Solution A: Calculate a wait period n based on the total size of the files transferred and throw up a wait window timeout n. This leaves my users helpless to click options in the form. It's just plain sloppy, and...

Newer Solution B: Use a do while loop to check the CarbonCopy Logfile for the 'job completed' message. In order to prevent constant out-of-control looping, a (you guessed it) wait window is included at some point in the loop to slow down the ol' fox - and there we are right back in the same boat.

Code-built timer control? OLE? What? Huh?

It's the apparent simplicity of this that gets me. Ya don't need to take me all the way there, but a pointer toward a path would be much appreciated.