Hi David

>The only time I ever put a program all the way into a READ EVENTS loop is when running the fullblown app.

Thank you for your reply. How would you test a form that needs a group of other objects to work? What I do is write a little .prg something like this and run it from the command window

PUBLIC gomyform1, goconstants, goerror, goapplicationdatamanager

goconstants = CREATEOBJECT("myconstantshandler")
* if there's an error goerror will make a messageform will display
goerror = CREATEOBJECT("myerrorhandler")
goapplicationdatamanager = CREATEOBJECT("mydatamanager")

*
* more stuff you don't want to know about
*

DO FORM myform name gomyform1

READ EVENTS

CLEAR ALL

... seemed fine except until 'gomyform1' is up (? until I issue READ EVENTS) I don't see my errors' info in the errormessage form that goerror creates. The errormessage form does display correctly, and its properties are correct, but it doesn't 'read' them into its controls. If the DO FORM myform line has run I do get the gory details on my very occasional <bg> errors displayed as desired in the errormessage form!

As you can see from the example I therefore still get all my _form_ errors displayed as desired. However as the form 'myform' is now interacting with the 'goapplicationdatamanager' created before it and I wish to do things to that object while the form Load()s, I now cause occasional errors in the 'goapplicationdatamanager' object to view and correct - while the 'myform' is in Load() and _before_ any form has displayed!

From which I thought maybe READ EVENTS was responsible.

But... perhaps wickedly running one VFP form from another's Load() is the cause of my pain.

Over to you...