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.

>All,
>
>Well, I finally got a chance to deploy something using the InstallShield edition that comes with VFP 7.0. Supporting applications in other versions had delayed this experience. My impressions: I think it's great and probably will try to get the full version. I found it easy to use, and Mike Stewart's "walkthrough" paper kept me from making some common mistakes (Thanks, Mike).
>
>The only problem I had was that I get what seems to be a rather spurious dialog saying: "Data size too small for system call" or words to that effect, with an OK button. The reason I say "spurious" is that the install goes just fine, except for this dialog. I've gone over the docs several times and can't seem locate anything on this. Further, trying different media types didn't seem to help either. Anyone run into this and found a solution?
>
>Finally, I want to thank the folks at MS for making this available. Even with the dialog, I've found it to be much more flexible than the old Setup Wizard.