I , uh, ... ahem..., ..shuffle.. meant that using an Assign method was the way I had actually done it myself.
hence the chagrined look on my face. do one thing, suggest another ;)

I even got sold on Access and Assign methods pretty quick.
e.g., I use the Assign methods for creating an "event" for control level "security" - what to hide completely, show read-only and allow for editing, based on the user level.
All my base classes have a CheckSecurity flag property with an assign method.
In the form base class, I simply call thisform.SetAll("CheckSecurity", .T.) and they all run their security checks, regardless of containment level. That way, each control is responsible for it's own settings, without ever having to call any specific controls.

>Hey Trey,
>
>;-D
>
>That's the way I used to do it until VFP6. And then I started poking around with Access and Assign and got to thinking .... hmmm ... if a flag denotes when certain controls are on or off or have certain captions, then why not make the changing of those controls bound to changing the flag? That way it's all centralized and I can change the state of the flag from any button or menu item or wherever and behavior is consistent.
>

>
>>< chagrined >
>>yeesh, that's even how i actually did this when i needed it myself....
>>< /chagrined >