Hello Tom,

Some answers for you...

1. The config.fpw has the temp directories in it as well as MVCOUNT=6000 (Foxfire requires this to be bumped up.)

2. VFP runtimes are located in the \WINDOWS\SYSTEM directory and registered via InstallShield when the old executable was put into place.


1. Both exe's have the same name.
2. The new exe overwrote the old exe in the correct directory (TARGET).


Note: The only change was the fact it was a new executable. Once the old executable was restored, speed was brought back to it's former (already pathetic) speed.

Gordon.




Gordon;

Are there any variables overlooked?

1. Config.fpw
2. Where are VFP runtime libraries located?

With problems like this it helps to become a third person and attempt to define and evaluate possible causes.

1. Do both exe’s have the same name?
2. Where are the exe’s located in relation to each other?
3. If the exe’s are in different locations and have the same name rename the newest and place it in the same directory as the old version and see what happens.

Tom