>
>Unfortunately, large parts of the Wscript functionality are only exposed to running instances of CSRIPT/WSCRIPT, and thus can only be used internally in scripts. I'm playing with ADSI, and think I can expose the ADSI objects inside of a VFP app, but haven't yet gotten things quie right. What I have done is launched Scripting Host scripts from inside a VFP app using CreateProcess(); I have VFP create the script file and then launch it using my API process class (you can take a look at the FAQ entry I did on LaunchAppAndWait() to see the general approach; I've working on a VCX that'll expose the CreateProcess() and ShellExecute() functionality in a more VFP-ish fashion.) I use volatile registry keys to pass results back from the script to the running VFP task.

That brings up an interesting point. I saw a message on the newsgroups about a VFP function runscript that when you type in a form or command window shows up as a keyword. If you try to run it though, you get an error message. I wonder if this is an undocumented feature that we've been mushroomed on, and if it might have some import here?