Hi Michele! Have you tried using CreateObject() to instantiate the AddressLocation object as well?
loAddLoc = CreateObject("MapObjects.AddressLocation")
...
loAddLoc = matcher.MatchAddress(Text1.Text)
Just a thought...
>I don't know what the method code looks like. It says it returns an object, and in the VB code, it "dim"s the result as an object.
>
>What I'm wondering is, if it _doesn't_ return an object, why would VFP complain loResult isn't an object. And if it _does_ return an object, why doesn't VFP just make loResult an object?
>
>And why can VB instansiate it as an object and VFP can't? Although that may be a MO question...
>
>Here's the VB code:
>
>Dim addloc As MapObjects.AddressLocation
>
>...
>
>Set addloc = matcher.MatchAddress(Text1.Text)
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
