>It's just the length of the list of omitted features - and this omission of XP is not on that list - which shouldn't have gone that far overboard. Actually, there are two things which tick me off - the fact that we have to include the VFP runtimes manually (is not a default, though being able to switch it off is actually good), and the whole mess about the way COM objects have to be included (you have the visible control's name, classname, filename, merge module name - and I still haven't seen a good list where to find them all in one place). At least a brief (not necessarily automated) version of the analyzer should have been included. Or a simple warning that the .exe uses some stuff which is not included.
>
>The way it is, you have a product which does build a setup, but you're not nearly sure it'll work, as you could be if the above was included.

Your points are well taken. I guess my POV is, consider the ISE limited edition to be a learning tool and, if it's at all possible budget-wise, spring for the full version of ISE for real work. It's worth it IMO.

Re which COM controls are in which merge modules, I also have not seen a good list all in one place. I thought about trying to build one by opening each of the merge modules with Orca to see what was inside, but decided it was more of a project than I wanted to get involved with.

Also there is a *gotcha* with Orca, that if you open a merge module its timestamp gets updated to the current date-time even if you make no changes. The effect of this is that when you install a product update that includes an updated merge module (for example, VFP7 SP1), the installer looks at the timestamp of the merge module on your disk and if it's later than the timestamp of the updated merge module then the installer assumes it's more recent and does not install the updated one. (Yes, I found this out the hard way.)