Thanks. I've solved the C++ MSM error... it was actually unrelated to that module.

Now with I try to run the Setup.exe on a WinXP system, I get an Error 1322, something about a path name exceeding the system's maximum allowable length (but it doesn't tell me the actual path name, so I have NO idea where the problem is).

???


>>Sergey, Wait! Now that I'm digging in, I have two more questions about installshield:
>>1. Why am I getting an installshield build error regarding the inclusion of MSVCR70.msm:
>>
>>Merging Microsoft Visual C++ 7 Runtime Library: C:\Program Files\Common Files\Microsoft Shared\Merge Modules\MSVCR70.msm
>> ** Error -3018: Error determining target for shortcut [ProgramMenuFolder]\##NEW_STRING6## in feature Always Install
>> ** Error -3018: Error building Shortcut table in feature Always Install
>>
>
>It's weird. There's no need to create shortcut for VC++ runtime.
>
>>2. How can I get installshield to NOT include the MTDLL support file? This is not needed and adds megs to the setup image size. Don't they have an "exe-support-only" version of the VFP7 run-time library?
>
>AFAIK, there's only one version of merge module(MM) for VFP runtimes. You can eaither include runtimes directly w/o MM or use Orca to create new MM w/o vfp7t.dll.