Colin is right. VFP code is asynchronous, which means it has to finish one task before it can start another.
That said, it is possible for the
user to interrupt a task, for example by pressing a key or clicking on a button. To do that, you need to put DOEVENTS inside your loops. Each time VFP comes to DOEVENTS, it will pause and look for an event (a keystroke or click) to execute. However, this approach will greatly slow down your code, and is not completely reliable (in my experience).
A possible solution would be to use an animated GIF, as I mentioned above. I explained how to do that in thread184-1818143. But that's not an ideal solution easier.
A much better approach would be to do as Colin suggested: do without the animation completely. Not only does it add no functionality to your app, it is a feature that many users are likely to find irritating - I know I would.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads