Pretty good idea you have as there's nothing in VFP to compile a list of these currently (some developers still have problems figuring out which runtimes to include at times). Each activex/dll/etc may have other dependencies that would also need to be figured in, but it's all very doable.

I use Instashield X myself, the dynamic scanning it has for my applications does a wonderful job of putting together a list for me and pulling in the necessary components for my install. I know that's not the solution you were looking for, but I figured I'd toss it in as related.

>Hi everyone,
>
>I've been away from VFP for awhile on other projects, but am back working in the Fox again.
>
>It seems to me that this should have been solved by now, but does anyone know of a simple way to determine all of the dependencies of a VFP project? I have Installshield Express (full version) and it helps somewhat by allowing the inclusion of merge modules, etc.
>
>Hasn't someone (Microsoft?) come up with a way to determine the ActiveX controls and external libraries needed for a particular project?
>
>It seems to me that you could read the Ole2 field of every VCX in the project, search all code for SET LIBRARY TO statements, etc and build a pretty good list of OCXs, FLLs and miscellaneous DLLs needed. You could then use Installshield to determine the deeper dependencies, like C runtimes, etc.
>
>Am I missing something or is this still a major problem for everyone using ActiveX controls and external libraries?
>
>Thanks!
>
>Steve