Tobey,

I just experienced a similar problem - the time to start my app for users with new, fast systems was up to over a minute - much longer than users w/slow, old systems.

I open many files at start up time...data is on an NT network.

A suggestion here was to check to see if an anti-virus program was running. yep. that was the culprit. on the new systems, temporarily removing virus protection allowed the system to start up in about 2 seconds!

One idea is to modify the files that the anti-virus program checks.

In my case, all users wanted to always start my app at system start-up time...so we added the app to the StartUp folder, and the time to start the app is folded into system start up time - less noticeable by the user while they are getting their coffee and getting settled in for the day.

hope this helps. J

>I have clients running an executable version of a VFP 6.0 app I designed and developed. All was working well until some of them started upgrading their computer equipment. Although the executable version is the same, starting up the application takes much, much longer on their newer, faster equipment than it did before. They are still in Windows 98 and were before they upgraded the new equipment. Those that have slower equipment get into the application in 7-15 seconds. Those that have newer, faster equipment take as much as 2 1/2 minutes to get in. Once they get in, the app actually runs faster on the new equipment. Any ideas on what's going on and what I can do to resolve it?
>
>Thanks in advance for your help.
>
>Tobey L. Miller
>Meridian Information Systems