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


>My user required a very minor change to the system I created. I made the change and supplied just the executable. When the user replaced the executable, the system ran three times slower than the old executable. This was confirmed when the old executable was restored.
>
>The effect of the slowness is not related to the changes made either. The main data entry form, which was not changed at all, became three times slower. All of the other forms as well became three times slower.
>
>Three times slower = 15 seconds to load the main form for old executable versus 45 seconds for the new executable (remember; no changes to this form!)
>
>I talked with the user regarding this and found that the executable was installed on their computer while the data is located on the network. This was the case with both the old executable and the new executable.
>
>I was wondering if the slowness could have ANYTHING to do with how the executable is registered on the Windows NT machine. I use InstallShield to install the software normally, but have yet to test this theory.
>
>The computer:
>
>Windows NT 4.0
>Pentium 4 1.6gig
>Lots of harddrive
>Lots of Network harddrive
>256meg ram
>
>Any ideas would be welcome.