>I've been going around in circles with Tech Support at MapInfo trying to get certain features in their MAPX object to work. The biggest obstacle is that they talk in terms of VB while I talk in terms of VFP. Can someone please "translate" what this VB user is trying to say in VFP terms?
>
>>>
>I found out that the SET keyword IS relevant.
>In VB, SET creates a pointer to the object on the right side of the equals sign.
>You could also say this as: SET gets an object into a variable by reference.
>
>So armed with this knowledge, is there a way to set a pointer on the left to an object on the right in VFP?
>If so, this is what needs to be done, I believe, to get this to work in VFP.
>
>Eric
>MapInfo Technical Support
><<
>
>Background info: Although I've been fairly successful in implementing MapInfo's MAPX activeX control in VFP, there are a few things that I can't get to work - and all of them have a common thread. That is attempting to explicitly assign an object to a MAPX property. For example, the Mapx object has a Layers collection where each item in the collection is a layer object. The Layers collection also has a property, called AnimationLayer, to which I can assign one of the layers. Something like this:
>
>oLayer=Thisform.Mapx.Layers[1].Item
>Thisform.Mapx.Layers.AnimationLayer = oLayer
>
>The equivalent to this code apparently works in VB, VC, Delphi, Domino, PowerBuilder, VBA for Word etc. But in VFP I always get an error, typically "Type Mismatch" when explicitly assigning an object to the appropriate Mapx property.

I didn't work with this OCX, so can say nothing, but could you test:
? TYPE("Thisform.Mapx.Layers.AnimationLayer")