>Looking through the MS WIndows Installer CHM that came with my ISE [I upgraded from the VFP LE version], I can't find this particular exact error. But just guessing from a similar topic, A buffer is too small to hold the requested data. So maybe a DLL or ActiveX control you are trying to install is not having its COM information exracted properly so it can be registered by IS. When you built the EXE, did you get any build errors? These would have been displayed at the bottom of the bottom frame that displays the build progress. You can look through the build results to determine what component in the project caused the problem.
>
>In the IS Project, where you specify what Files to install and where, you can right click on any OCX or DLL and go to the properties [any file actually]. On the Advanced tab, you can specify the registration type.
>
>If that is not the problem, you might try removing 1 merge module at a time to see if it is a bad module.

There were no reported errors during the build. I didn't have any DLLS, and the OCX's I used were included in the merge modules.

You may be right about the merge modules, but I'd think not. I will try that, however. Once installed (on a virgin machine) the program functions normally, including the OCX's. One disconcerting thing about the merge modules was the appearance of multiple instance of the same module (same name, description, etc.) for several components like the VFP runtime.

Thanks for the suggestions.