I'm assuming that this is what you received when using the VB to VFP converter? The VB to VFP converter is still in its infancy and as such it handles some of the mundane tasks of converting VB code, but is far from being comprehensive. I usually run VB code through it then go back and edit the rest by hand. When time presents itself, I will be improving on it, but between billable work, the upcoming Southwest Fox conference, and some VFP articles I am writing for the industry rags, time is a precious commodity these days. <g>

I believe that Christof's conversion code was pretty accurate (it will get you close to what you want if nothing else). Once you understand what the equivalent is in VFP for a line of VB code, it is usually just a matter of a whole lot of cut-n-paste.

If you, or anyone else for that matter, find conversion elements that are not handled properly by the converter, but have an idea of how it should convert them, feel free to email me and I will include them in the next version of the VB to VFP converter.

>Thanks for the help Craig, but I was wondering why the VB line:
>
>

>Set oSvc = New AddressSvc
>

>
>Is converted to:
>
>

>oSvc = New AddressSvc
>

>
>Which obviously does not compile in VFP. If I change it to:
>
>

>oSvc = "New AddressSvc"
>

>
>It destroys the object created with:
>
>

>oSvc = CreateObject("Avalara.AvaTax.Adapter.AddressService.AddressSvc")
>