>>>I've just had a problem with this myself - I can't find VFP500.DLL anywhere and can't remember how I generated it last time. I will have a hunt around and let you know,
>>
>>I was thinking of a possible way. From what I read, it gives you the option to include them in the installation program. So what if I made an installation program that didn't actually install the app, just the runtime library? Would that work?
>>
>>Thanks,
>
>Doing that would install a whole bundle of DLL files which you don't need - what you could do (and what I intend doing) is create an installation of a small app, install it on a spare PC and take off the files you need (VFP500.DLL & maybe the files Sanjay mentioned) and put these in your windows\system directory - create a backup of these files for future. You should find VFP500.DLL and .ENU in your windows\system directory - NOTE: I can't find them on my PC (NT4) at work but they are here at home (W95)!

what we do is create the setup images on a directory that has only one file (usually readme.txt or config.fpw). we use these images to make sure our programs can find all the libraries they need. for vfp5 i think there are 4 files required. the rest of the files in the setup system are used by setup.exe.

doing this also ensures that the libraries are added to the registry.