So would that mean that there's no guarantee your solution is going to pause the program during a loop? It just sounds kind of hit-and-miss. How do you really know when VFP will decide to respond to the event?

In any case, your answer didn't really clear things up. The form is just sitting there - no lengthy SQL statement or anything else to keep it busy - yet it will not respond to an event outside VFP. I thought I had seen articles on BINDEVENTS where it suggested you could use BINDEVENTS to respond to a keypress anywhere in any Windows app. Perhaps the technique used needs to be changed for that to occur or perhaps I'm not remembering that article correctly.


>BINDEVENT works much like timers in VFP. They only fire when VFP checks for them while being idle, having a DOEVENTS, and the like. The code is not executed, for instance, when VFP is running a lengthy SQL statement.