I suspect it's because the new EXE added a PRG and modified a the structure of a one record DBF.

Almost ready to do a new MSI. I am thinking the registry has some kind the map for the (original) installed MSI EXE, and therefore does a lot of "searching" to make sense out the EXE that overlaid it.

>>I am Terry's Carbon Unit
>
>LOL. Please keep references to your unit to yourself out of this family oriented show. ;) If you meant some obscure Star Trek reference, we are all Carbon Units. Lt. Ilia carbon unit was replaced by V'Ger recreation - which was no longer a carbon unit and referred to life forms as carbon units infesting U.S.S. Enterprise, and by extension, Earth and other planets.
>
>I do not use procedure libraries. I put each function as its own .PRG. These are found directly by the exe. There was a time that issuing SET PROCEDURE TO was a performance hit. That has been reduced.
>
>I have not seen any performance hits caused by replacing old exe with newer one with my setups. I'm using InnoSetup.
>
>
>>
>>LOL
>>
>>>>The IDE FXP crunch performing better than the EXE crunch is unexpected - seen it before - it went away - the cure may be to simple rebuild the MSI and do a proper install.If it was an issue of doubling up or multiple passes then it seems that would present during the IDE FXP tests.
>>>>
>>>>Any thoughts appreciated.
>>>>
>>>>It's not
>>>
>>>Who are you and what have you done to Terry?
>>>
>>>Real Terry would have at least 35 spelling errors in a text of this size. You made just this token error, but that is not a good disguise.