George,

I am not sure if this will help any, but I just want to let you know. I converted 4 ISX projects to the VFP8 LE Version of InstallShield. And all work fine but 1 project. I can't remember what was the error now. And I couldn't find any solutions or causes of the error, so I got the OCRA tool from MSDN site to debug. And voila, I saw an empty line in the ISX project that was causing the error. And it's fixed after I removed that entry and rebuild the project.

So try the OCRA, you might see something interesting in your installation too.



Wan



>>George,
>>
>>Sorry it didn't help out.
>>
>>My lastname is Wan, firstname is Cheang Hoong. And yes, you're right about asians' name. We do have our lastname first, so in my case, I would have my name as Wan Cheang Hoong when I am over in Asia. Since I have been living here for 9 years and I am working with Americans now, I just follow the "culture" and put my firstname first. :D
>>
>>And I go by Wan, it's easier to pronounce.
>>
>>
>>
>>Good day.
>>
>Wan,
>
>< bg >Well, there's no reason to be sorry. Somewhere, in the depths of those article(s) you pointed me to, is the answer and once I find it, you'll know about.
>
>The funny thing is that this is a VFP 7.0 app (not 8.0 because I have to support Win95), that had a setup that ran perfectly fine in the previous version. I had to make some modifications to it because of the location of the target machine. I've even built a new project trying to resolve this error (thinking that something when the original was coverted got messed up).
>
>Thanks for the help.