>>>>Yes, thank you, this version works. Did I understand correctly, that every reference to WScript (at the beginning of the line) in the samples has to be converted to an Windows-API call?
>>>
>>>Yes, I have it found at "Q259103 - HOWTO: Use the Windows Scripting Host to Automate an Application". It seems to be that Wscript object accesible only inside the Windows Script Host and not creatable by OLE.
>>
>>Thanks, again. Now, having to invoke the WinAPI for different functions looks too complicated to me. It seems to me I should rather a) Run scripts directly (for instance, I can create a file with Visual FoxPro - copy the samples, as is, for a start - and run it), or b) Study the WinAPI, and run it without the W. Scripting Host.
>>
>>Hilmar.
>
>< SET $0.02 ON >
>I would use the integrated approach when available. WSH, ADSI, WMI, etc. are great COM-based wrappers to the WinAPI. A lot of the WinAPI functionality that would require memory management and structure manipulation has been incorprated into those packages with an easy VFP friendly interface.
>< SET $0.02 OFF >
>
>Regards.

Please, what does "ADSI" and "WMI" mean?

Hilmar.