>>I have another question. The signature for the method is this
>>
>>

>>static public string VerifyAddress( ref string AddressLine1, ref string AddressLine2, ref string City, ref string State, ref string ZipCode, ref string Country)

>>
>>So, although it may be not a good practice, my colleague (who wrote this method) returns new values using parameters passed by references. When I debug that DLL, I can see the new values, however, my call
>>
>
>I see Rick already replied, but normally if I have access to the underlying .NET source code I end up creating my own wrappers for things like this. For example, I'd create another VerifyAddress method (sorry, but yuck!) as:
>
>

>public static Address VerifyAddress(Address address)
>{
>    // Code to verify address here
>    // Create new Address class and populate properties, then return it.
>}
>
>public class Address
>{
>    public string AddressLine1 { get; set; }
>    public string AddressLine2 { get; set; }
>    public string City { get; set; }
>    public string State { get; set }
>    public string ZipCode { get; set; } 
>    public string Result { get; set; }
>}
>

Hi Paul,

Thanks a lot, that's exactly what I was thinking as well and hopefully it would not be a problem of reading these properties back in VFP.

The only hard part here is to ask my colleague for that favor :(