>>I seem to need the read events command to start event processing, but through the years, my program craps out many times at this command which I issue in the main prg. What is the deal with the read events command? What actually is it for and why does it seem to give me so many problems?
>
>The READ EVENTS command will establish a sort of "infinite loop". It will wait for user input. When an event occurs, VFP will process it, but then go back to the READ EVENTS, and wait for further input.
>
>To quit this "loop", use CLEAR EVENTS somewhere, for instance, from the menu item "File | Quit" in your menu.


Actually, that is where it will not exit the read events. I have an exit button on the form and I have clear events followed by a release thisform, but stepping through the code, when it hits the release thisform after the clear events, it rolls to my form.activate and stays at the read events and loops. Why would the clear events before the form release prevent this from occuring?