>Hi, folks...
>
>I'd offer a case of beer for the person who can help solve this mystery, but since I'd drink it first, all I can offer is verbal gratitude!
>
>We have an application that polls an FTP server all day long for new uploads. (We use Mabry's ActiveX control for FTP access.) The app polls, pulls down new files, does some posting, and puts results back on the FTP server.
>
>Quite often, the app appears to 'freeze', and requires someone to tap the mouse to get it to resume processing. It happens at different points of the app, so I've never been able to pinpoint it. I've put a ton of DOEVENTS() and mouse-moves in the app, but to no avail.
>
>Unfortunately, some view the app as dysfunctional because someone has to tap the mouse to get the app to 'wake up'. ALL power mgmt features on the machine have been disabled.
>
>I have to wonder if it has anything to do with using an ActiveX control, but don't know for sure. (I'm using VFP 5, and am doing the AUTOYIELD = .F.).
>
>Any clues?
>
>TIA,
>Kevin

I'm doing the same thing you are. I found out that I had to stick the DOEVENTS() in a DO WHILE loop. i.e.

DO WHILE !bDoneEvent
DOEVENTS()
ENDDO
bDoneEvent=.f.

bDoneEvent is a public boolean flag to indicate that the DoneEvent in the Mabry control has fired. I flip the bDoneEvent flag to .t. in the DoneEvent Method. I was getting the weird behavior you were describing until I realized that the DoneEvent hadn't been accessed yet in the Mabry Control, but the DOEVENTS() completed. This should take care of the problem.

Tom