>
>When we assign a property an object, it is no longer a property, but rather an object. There's no place in the VFP documentation that says an object can have an _assign method. In fact, by trying to create this sort of thing, we may be actually corrupting the object model.
>
>
>I don't know if this statement is correct. It is still a property but it is a property that is a reference to an object.
>
>Also this is cut from this link.
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fox7help/html/dggrfCreatingAccessAssignMethods.asp
>
>
>
>In the Form Designer, you can create properties with Access and Assign
>methods only for a form or formset. To create properties with Access
>and Assign methods for a control or object, use the Class Designer to
>create the control or object class. In the Class Designer, add properties
>with Access and Assign methods to the control or object, and then add the
>control or object class to the Form in the Form Designer.
>
>
>
>George with that said would it be safe to say that _assign method is intended to be use on Reference Members / Instance Variables / Properties (What ever you want to call it)

Bob,

I'd have to say so. Simply because of proper encapsulation, if you don't want to create an object, you shouldn't let factors outside of that object make the determination.