>>>Thanks for that!
>>>
>>>Does that install the VFP libraries too?
>>
>>It installs anything you tell it to :)
>>
>>Here's a sample script (I've cut out some code that allows the user to select where the installation goes, so if you get trouble let me know):
>>
>(snip) (snip) (snip) (snip)
>
>I see by the Source lines for the VFP runtime libraries there is a reference to "c:\Program Files" folder -- which indicates to me that you've got a 32-bit version of Windows. If you switch to a 64-bit edition of Windows you'll have to change the "c:\Program Files" to "c:\Program Files (x64)" -- in that case you might want to consider making copy of the runtime files into a different folder, then change references to that folder. That's what I've done at work because there is currently a mixture of 32-bit and 64-bit systems used (I have not yet migrated the entire development team to 64-bit Win7) and I didn't want to have to change the setup scripts each time I was building an install set.

On 64 bit machines it is actually c:\program files (x86).

I'm a lone developer so it's not a big deal for me, but thanks for the idea