>could someone point me to a good explanation of the read events / clear events cycle?
>i've been doing pretty good with it, but really just getting things to work and not quite understanding why they work that way.
>
You need READ EVENTS in your app to create a wait state and process events in the app. The form itself may be run from Form Designer without READ EVENTS, but if you run app and there is no READ EVENTS it will just flash and end.
You issue CLEAR EVENTS somewhere in app when you would like to terminate the app, so there will be code executed (if any) starting the next line after READ EVENTS (usually some closing procedures)
HTH,
Nick
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison