>I was just asking because this thread has made me curious about where/when/why to place READ EVENTS command...
>

There isn't just one answer to that. As usual with VFP there are a few ways to go about it. When I have an app that uses a login screen, I make the login screen modal, and don't do a READ EVENTS until after the screen is closed. One advantage to this technique is that I don't put up the menu until after the user logs in. If there are any menu options that change their availability based on who has logged in, I can set that up before showing the menu at all.

If your login screen is the same as the splash screen, and is a top-level form, then it can't be modal, but you probably don't have anything else on the screen at that point anyway.

IAC you do need a READ EVENTS to create a wait state if you don't have a modal form displayed.