>on the basis of which I feel safer leaving it to the OKL's.

You shoudl NEVER feel sfaer with OKL's. They can interrupt running code and cause some very serious bugs that are very difficult to track down. What if you get teh OKL to work and the validation for textbox is running when the suer hits the OKL key? The focus will jump to the page without completing the valid code and possibly fire events associated with teh focus change before the currently running valid code finishes.

OKL's can be extremely beneficial if you need an intercommand interrupt But if you only want it to work when the system is in a user input mode, OKL's can kill you.

>Any thoughts about the out of scope formname?

I'm not sure of what you mean by the scope of FormName. Forms are objects and that means theree are three different things about them that are commonly referred to as the name. There is the file anme of the SCX, their Name property's value, and the name of a variable or property that holds an object reference to them.

The one that folks usually are talking about in relation to going out of scope is the object reference. The solution is to use a permanent object reference that has the same lifetime as the fomr itself. The best way to accomplish that is to use a form manager object to launch all of your forms and have that object keep an array of object references and identifying informatrion about every form that exists. Then you never try to address any form directly, you ask teh fomr manager to forward the message for you.