>>If you don't have MSMs for the controls of interest, then you'll have to manually include them in the distribution set, along with any dependent files such as DLLs that they may require. I'd suggest looking at www.installsite.com for some ideas.
>
>Maybe Installshield express limited Edition don't do this.

I know ISE Ltd can work both with pre-created MSMs, and will permit you to specify exact files on a file by file basis, and specify install behavior such as which directory they end in and any required behaviors such as registration. It's not a completely automatic process. ISE Ltd does not have an internal mechanism to build MSMs as a tool for reusable installation design, but will accept and apply MSMs if they're specified. You can create MSMs with other tools - I use InstallShield Pro for Windows, so I have this capability; ISE (retail) has a wizard-driven MSM facility, and there's always Visual Studio Installer, which can be downloiaded from the MSDN web site, and used to create MSMs, who behaviors are adjustable with the ORCA editor included with VSI.

You have to know what you want to install and what these things require at some point; the ISE Ltd is focused on delivering and packaging VFP, not with producing the external mechanisms for delivering other products.

>>Why do you have 319 files in your distribution set? If you've compiled to an .EXE file, and that .EXE file is made up from hundreds of different components (PRGs, VCXs, OCXs, etc, you only need to distribute the executable, not all the source code modules. If you have large clusters of files whose content is static, you might consider compressing them into a .ZIP or .CAB externally to reduce processing time.
>
>
>I need to distribuite some .exes, tables, and some .jpg files.

I suspect that you are either tight on memory or disk space; I run ISPro, and have used ISE, on significantly larger projects, and assuming that adequate disk space is available for temporary files and to manipulate the tables used to produce the install set, on much larger projects in far less than 13 hours. It takes a few minutes for ISPro to prepare a distribution on the machine I'm working on consisting of about 700 components, most already bound into MSMs or self-extracting file sets, and this is not exactly the world's fastest box - it's dual PIII/550s running under XP Pro, but it has lots of RAM (about 768MB) so that it hits the disk very little during the asembly procedure.

Have you tried using ISE Ltd on a smaller project first to make sure it's working properly, or is this your first shot at ISE Ltd?