Thanks for the feedback.

As you say, if VFP does something easily all the better, but I'd like to learn how to do things with the "seven league boots" that sometimes those tools offer, plus sometimes one is not using VFP at all. These tools are easier to use than DECLARE etc since intellisense becomes available.

Let's see what others here may suggest. First I am looking to understand what each tool does well and perhaps choose one that is easiest to use and is generally available or easy to install at customer's sites. In the past I was scared off from WSH because some viruses took advantage of it, but I think that has been overcome by MS.

Alex


>As you asked me directly. The newer technologies are normally the fancier ones with the newest bells and whistles, but will perhaps not be available anywhere.
>
>That does not mean to avoid eg Powershell. But additional to making use of any scripting you need take care of redistribution. If there is no good gain I tend to avoid anything that I can also do with VFP alone. Scripting.Filesystemobject is indeed rather helpful, for example when it comes to wrinting files with the capitalisation you want, or in your problem copying files, VFP won't let you, like an open DBC.
>
>WMI offers functionality you would need to do much programming, nevertheless I did have a use for that only once.
>
>Sometimes old bat or cmd files are still the easiest way to do some things, XCOPY or SUBST are much easier to use than WinAPI calls.
>
>I'd be interested to hear from others too, what they use and for what tasks.
>
>Bye, Olaf.