Is the MSI and IDE on the same PC, running against the same database?

>Hello,
>
>When testing new EXEs, my practice is to save the build to the folder of the the most recent version (MSI) the new EXE will replace. I use this practice for a variety of reasons: One is to avoid cluttering up and then having to cleanup default DBF store states. Another is to take advantage of any data the legacy MSI might contain for testing.
>
>I know there is a difference in the behaviors of an installed (MSI) EXE and an EXE that runs in the IDE (VFP window).
>
>For example, this particular project implements some very tedious calculations. A few years ago some really tedious iterations were added. IDE testing raised an ERROR 78 (so called domain, or exponential function error). When the MSI was tested, ERROR 78 never happened. The solution (i think) was to make sure a copt of the C7runtime DLL was in the development folder.
>
>My issue is speed. When testing in the IDE using just FXPs (not an EXE), the application seems to crunch the numbers about 3 times faster than the EXE copied into the MSI folder.
>
>Before each computational pass the app implements:
>

SYS(3050,1,1)
>SYS(3050,1,uiFGMemory)
>
>* Note: uiFGMemory=INT(VAL(Sys(3050,1)))

>
>Config.fpw looks like this:
>

resource=off
>refresh=0,0
>help=off
>progcache=0
>mvcount=65000
>stacksize=65000

>
>The Legacy app seemed to deliver better performance when it was initially installed (too lazy to build a test MSI to verify).The computations are the same (TRY CATCH routes to less tedious alternative computations should the "desired" computations cause stack problems)
>
>Is my practice of over writing an MSI installed EXE effecting something in the registry that would explain why the FXP(s) in the VFP IDE window out perform an overwritten EXE in the MSI Program Files folder?