>The 32bit version - according to the Tech Support requires:
>
>errormsg=ABC.InitializeDLL(where ABC is the object ID)
>
>Ed says: "oHPA32N=CreateObj('Hpa32n.dllClass')
> errormsg=oHPA32N.InitializeDLL()" will work - and it does. That is I don't get any errors.
>
>I had misspelled "CreatOBJ" - sorry ED.
>
>But now how to pass the parms?
>

Just like you would to any other COM object in VFP - as a comma-delimited list of arguments passed in the parentheses.

cWhatisYourFavoriteColor = "Red...no blue"
oMyComObject.SillyObj("a Character Literal",@cWhatIsYourFavoriteColor,42)

would pass the string literal and the number by value, and would pass the variable cWhatIsYourFavoriteColor by reference, so that if anything changed the value, the revised value would come back to VFP.

VFP uses a fixed sequence of arguments to a method - if the VB examples use named parameter passing, you need to know the expected order of the variables. This can only be answered from the documentation.