>Hi Ed and all,
>
>Progress. I have a errormsg returned: can't find the .dft in the specified path.
>
>Spoke to Tech Support. He states that the params lcPath etc. must be prefexed with the object name like: oHPA32N.Path = 'D:\HPA'. But if I create the parms before the CreatObj statement oHPA32N.Path the object is not found and if I create them after then the @oHPA32N.Path in the creatobj statement causes an error.
>
>VFP is not letting me describe a variable with the object name before defining the object or not letting me use the variable prefixed with the object name because it's not yet defined. Catch 22? How to get around?
>
>In VB He:
>
>Dim ABC As HPA32N.DLLClass
>Set ABC= HPA32N.DLLClass
>ABC.HPAPath = TXT_HPAPath && where I guess he storeed the path
>

oHPA32N = CREATEOBJ('HPA32N.DLLClass')
oHpA32N.HPAPath = "fill in the path"

IOW, it works exactly like any other automation object. It uses the same kind of syntax to set values in the object and retrieve values from the object as any other object you've worked with. It has properties that you can manipulate just like the properties of any other object...

It has that can be invoked, in some cases with, and in other cases without, parameters. It may or may not return a value. Just like methods of every other object you've ever dealt with. Why is this hard? It's a COM Object. The object has an automation model - properties that can be read and written to, and methods that can be invoked. THERE IS NO INDICATION THAT IT BEHAVES WIERDLY.

Have you tried dealing with it like you would any other object? The fact that it's a DLL doesn't matter - so are lots of other objects. You could write a VFP COM server to be a .DLL, and it would act exactly the same way - you create it with CREATEOBJ(), assign and read properties, and invoke methods. THIS IS THE SAME THING.