Michael,

the _Screen hook problem is well know for months now. We have discussed this several times and once microsoft says something like that the example in help was a failure and that the whole idea was a not good.

To me, the idea to use BINDEVENT instead of the hook kludge is much better.

Update:

There are open questions using BINDEVENT on _SCREEN.RESIZE, for example the eventbinding will not fire if you change the size of an docked window.

Agnes
>>>Now in VFP8 that raises an error, Object oScreen not found.
>>>
>>>How should I capture the _screen.RESIZE in VFP8?
>>
>>Agnes gave you the answer for this: I just wanted to let you know that it was an intentional change on the Fox team's part to increase stability - code like the above could cause C5 errors in some cases.
>
>For the record, Garrett, I've been using _screen hooking extensively under VFP6 SP5, and I have never experienced any C5 errors attributable to this. Microsoft's use the term "stability" is curious: the first definition of "stable" in my dictionary reads Resistant to sudden change of position or condition. Perhaps it would be better to find a different euphemism to describe the situation.
>
>Mike