Hi Charlie.
I guess you're the only one guffy enough to respond to such a trivial issue. :)

One thought I had about your response.
Even if you wrap DODEFAULT with This.ScreenLock =.t. and This.ScreenLock =.f.,
All objects still get refreshed, but it will keeps the screen from blinking. Is this correct? If so, the user still has to wait until all objects has been refreshed.

Thanks Charlie.

>Hi Dean,
>I think you may be guffy and partly right. :)
>The default VFP behavior is to round up all the controls on the form and refresh them when a Form.Refresh is >executed. You can control the Refresh with a NODEFAULT
>PROCEDURE frmBase.Refresh()
>NODEFAULT
>This.ScreenLock = .T.
>DODEFAULT() && The default behavior will occur here!
>This.SchreenLock = .F.
>RETURN

>PROCEDURE frm2Class.Refresh()
>NODEFAULT
>* More commands
>DODEFAULT()
>RETURN

>>Hi.
>>I notice something yesterday as I was experimenting and I want to know if what happened is common.
>>
>>I have a parent form class that I use to create my forms. When I issued a DODEFAULT() in the REFRESH method of my forms, every object on the form gets refreshed multiple times. Thus, I must leave the REFRESH method clean and free of any code if I want my app to be clean. Am I guffy or am I right?
>>
>>Is this odd or what? :)
>Charlie