>>2- Write an .FLL to do it, and let it make the DLL calls. I'd rather kiss a snake.
>
>It's not that bad... You just have to have one of two supported (now obsolete) compilers.. I used Watcom C; but the geniuses at Sybase nuked the Watcom C compiler division...

The functionality of FLLs has been problematic for me; I'm immensely happy that VFP can have some limited direct access to standard C-style .DLLs via DECLARE...DLL, and the option of wrapping detailed operations in the APIinside a COM server is amazingly attractive. It's nice being able to make simple, easily comprehended and documented use of the wide range of COM services now at hand. WSH is just a stepping stone - the Wscript.Shell and Wscript.Network objects are far simpler to deal with and explain when shell and network related services are needed; the Scripting.FileSystemObject offers exactly the set of services I need for manipulating drives, files and folders in a simple and consistent fashion, and, lord help me, I've become a Vbscript.RegExp junkie in the past few weeks; lots of painful parsing and conversion work is a piece of cake, and will wonders never cease, uses the conventions I'd learned already from some distinctly non-MS environments.