Hi,
Have a look at http://fox.wikis.com/wc.dll?Wiki~VFP9RuntimeFiles
Some of the files need to be in the app directory i.e. msvcr71.dll & the report builder etc.

What you are trying to do may give a smaller inno setup exe, but it would lead to
a lot of possible errors.

You need to control the full install not just part of it.

Also why not compile the app and distribute that, more secure.

>I have admin rights. But I am confused about registering the files with versu
>without using innosetup. I think the examples you gave would be a line of
>code that is included in an innosetup file. Is that correct. I was assuming
>however that I could point the user to the a website where the foxpro run files are,
>tell her to download and install them. Then have a separate innosetup file that
>only includes the program files. This allows the innosetup file to be smaller,
>because when you include forpro runtime files in it, it gets much bigger. But
>I am beginning to see that the foxpro runtime files, even after you download
>and install them, they still need to get registered. So I guess the question
>becomes, when installed, where do the foxpro runtime files end up getting placed,
>which folder? Then, tell the innosetup file, to look for these files on the
>user's machine, and register them. But can you tell innosetup to do this, to look
>for dlls on the users machine?