>Hi Ed,
>
>Thanks for the response. I have installed the .dll. I have 'Declare'd the functions. VFP recognizes them. Display Status lists the functions. I have not used third party .dll's with VFP - yet. The documentation shows this example for the Initialize function:
>
>erromsg = ABC.InitializeDLL ( where ABC is the Object ID)
> (Returns the following data, comma delimited)
> Error code
> Module that returned the error
> Filename
>
>Set properties
>
>40 HPAPATH
>20 Profile
>8 Password
>
>
>Get Properties
>
>14 Settings
>6 DBDate
>5 Version
>
>
>How do I translate this to VFP 6?
>

The syntax is essentially identical in VFP:

ABC = CREATEOBJ('HPA32N.DLLClass')
errormsg = ABC.IntializeDLL()

>I've created objects for word and excel:
>
>oWordDoc = CreateObject("Word.Application")
>

So now you do a CREATEOBJ() of their object...

>The tech support for the third party dll (knows VB but not VFP) states that I should just translate the following to VFP:
>
>erromsg = ABC.InitializeDLL ( where ABC is the Object ID)
>

See above. You don't have to name the object variable ABC. oHPA32N seems like a good, unambiguous name.

>
>But this doesn't do me any good. I need to know how to define/setup whatever for 'ABC'. I believe it needs the Set/Get properties - right? How to create an object for that?

Set/Get are the VB equivalents for assign and access methods for a VFP native class. if you know the properties of the object, you should be able to assign values to and read values from them directly, or worst case, you'll have methods like ABC.SetSomeProperty to assign it a value and ABC.GetSomeProperty to read the value in it.

You don't have an API to deal with, just an automation model. It's just like using any other class, with properties and methods.