>What does your method code look like? If the method returns an object then loResult should certainly be an object.


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)


Thanks,

-Michelle



>>I'm not sure if this is a Map Objects problem or a VFP problem, but maybe someone can help.
>>
>>There is a method that returns an object. I want to do:
>>
>>loResult = method
>>
>>VFP complains that loResult is not an object. Shouldn't loResult be whatever the method tells it to be?
>>
>>Doing loResult = CREATEOBJECT() is not an option because it tells me the class definition doesn't exist.
>>
>>Any ideas?
>>
>>-Michelle