Hi Arnon,

Looks like we both are headed in the same direction. Maybe I had not understood your response correctly earlier.

Just one of those things... :)

>Hi Kamal,
>the point is exactly that they are wrapper methods around a protected properties
>it is basically implementing the same code with a nicer interface
>for example should you use an ActiveX Control in VC or VJ
>
>as for THIS_ACCESS, if you are implementing your encapsulation using protected properties (i.e the "old way") you can create such an "Event" by placing a call to an object "access" method on each SET and GET method you implement
>
>When, for example, we look at ActiveX controls we can see that this is exactly what I am saying
>if we drop a Slider (from comctl32) in a VFP form we can do it like that :
>
>this.Slider1.left=10
>this.slider1.top=10
>this.Slider1.TickStyle=1
>
>should we drop the same ActiveX control on a VJ form
>we sould have to do :
>
>this.slider1.setTickStyle(1);
>this.slider1.setLeft(10);
>this.slider1.setTop(10);
>
>this means that in VFP (and VB) we are seeing the ACCESS/ASSIGN interface for these protected properties and in VJ (or VC) we need to use the wrapper classes directly
>
>again,I'll say that I think ACCESS and ASSIGN are a very nice addition to the language, which I hope will encourage VFP developers to create more encapsualted controls (that is - use more "protected" properties because the interface of getting to these properties is cleaner)
>
>there are some very nifty implementations for these methods
>but I still say that this is not new functionality
>
>- btw, I may have to take these last words back , as it seems I can bind an ADO recordset to a grid (without converting it to a cursor) using ACCESS and ASSIGN methods and I currently can't reproduce that using methods (I didn't have too much time to check it though)
>
>
>Arnon