I tested having this in a procedure file (I used _SCREEN.Resize however) and it was not respected in VFP 5.0 when I resized the main window. I also tried it as a procedure of the currently executing program, also was not respected.

I have a feeling that what happens when events happen is that VFP does something similar to a PEMSTATUS() on the event and if it doesn't find anything, it walks up the class heirarchy until it does or until it gets to the top, then it does the default action. Tying via a procedure file doesn't make the procedure show up via the PEMSTATUS() (or whatever actually happens, but I imagine that it's something similar).

>
>I'm just speculating right now (on a trip, no VFP access) but why not a PRG with a PROCEDURE _SCREEN.Caption_Access or whatever _SCREEN property? If the PROCEDURE is run within an app, would it be respected? Can somebody here on the UT test this? I can but not until Friday.
>