Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
HPA DLL
Message
From
30/11/1999 21:21:40
 
 
To
30/11/1999 16:55:33
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Title:
Miscellaneous
Thread ID:
00296825
Message ID:
00297201
Views:
44
>Hi Ed,
>
>Thanks. I guess I have not worked with COM where I had to pass parms.
>
>But your example told me what I neede to know. This works:
>
>oHPA32N=CreateObject("Hpa32n.dllClass")
>oHPA32N.HPAPath = 'D:\HPA'
>oHPA32N.Profile = Space(19)+'1'
>
>ETC.
>
>ErrorMsg = oHPA32N.IntializeDLL()
>
>? ErrorMSg Returns '00 OK' now.
>
>Thanks for everything. I thought the parms had to be passed within the (..) in the CreateObj statement.
>

They aren't really parameters, they're properties - it happens that you can pass in parameters (arguments supplied to a function or method invocation) that are stored in properties of the object if you pass them in when the object is created.

>The difference between the Set Parms and the Get parms is that once the object is created the get parms are available via ? oHPA32N.Settings or lcSettings = oHPA32N.Settings. Which I am now able to do thanks to you and the others.
>

Yep, just like other properties of both COM and non COM objects.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform