>Ok, that makes sense, I think. So READ EVENTS doesn't really have an effect on form & coding that has user interaction? You can run forms, display data, fire WAIT WINDOWS, etc WITHOUT a READ EVENTS?
>


The READ EVENTS allows the form or the menu to actually be processed. So you need it (unless the form is modal).


>So therefore, READ EVENTS is sort of like a transaction processor... start here (READ EVENTS), store stuff until the end (CLEAR EVENTS) and committ those changes?!? - now wait, that doesn't sound right... maybe I should just leave it alone the way it was and not try to understand it... cept I'd like to...
>
>Am I Close?
>
>
>p.s. In my case, MYSYSTFORM "is" a modal form and it is before the READ EVENTS, so how is that affected?
>

A READ EVENTS is not needed for a modal form. In the program (or form) that calls the modal form, processing will "wait" at the line that calls the modal form.