>With prior versions of VFP, you could hide properties in, lets say, an Application object and call only methods if you wanted to. With VFP6 and Access and Assign you can do the total opposite.
>
>The VFP documentation, in describing the benefits of Access and Assign, states:
>
>"You can create a public interface for a class or object that separates the interface from the implementation"
>
>This is true and cool. For example, if you wanted an opentable method in your App object, you could add a custom property ("OpenTable") and a custom method ("OpenTable_Assign").
>
>From elsewhere, you would just set the property: oApp.OpenTable="mytable"
>
>The OpenTable_Assign code would be:
>

>LPARAMETERS vNewVal
>IF TYPE("vNewVal") = "C"
>   USE (vNewVal)
>ENDIF
>

With more TIPS about VFP6.0, we are becoming more excited it. Can't wait any longer for its actual release. Keep up the good work John.

BTW, do you have an idea for additional publishers writing books about VFP6??