>Incidentally, do you ever notice that sometimes it seems that foxpro seems to get ahead of
>itself, or it goes to fast to update certain things even though you seem to be putting code
>in to do it? I had a form which had a progress bar that showed the progress of a certain
>process. I had purchased the Dynazip activeX control which was also on my form a before I
>would even instanstiate it at all, I would make my progress bar visible again and reset it
>to 0% completed. Then I would instanstiate the dzip control. The progress bar stayed at
>100% as if it was still showing the first process'es completion. What I did to fix it, and
>I'm sure there is a better way, was to just put a WAIT TIMEOUT 1 right after I had reset
>the progress bar. That made it act as it should. I thought that's what was happening here
>but I was wrong. Do you have any technique that you use to fix the above though? Thanks
>again Jim -Rick

Rick,

The _TALLY was 0 becasue append blank doesn't update _TALLY, sql SELECT does.

What you were seeing witht eh progress bar is the fact that VFP will not process events while it is running code. You queued and evetn to teh ActiveX control and then fox just kept on keepin' on and the event remained in the queue until fox was finished.

The commadn to tell fox to stop and process events is DoEvents. Although you want ot use that comadn sparingly because it processes all window events and can slow your code down drastically.