You know, I've often wondered about the 'Read Events' clause myself over the years. Is there ever a time when processing is not desired? Why doesn't VB need it? I realise it's been like this forever, but I never really understood why an event driven language, which VFP purports to be, needs this. Why isn't it simply automatic like it is in VB. Afer all, is there a situation when one wants to write programs using only modal forms, or to have the form simply flash on the screen momentarily before the program ends? To put it another way, how many programs have you written without 'Read Events'. Personally I can't recall ever having done it.

To the best of my recollection, it was never required in Delphi either.

Alan

>>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.