I've had a similar situation when I moved a project to another machine+network - I still had references to old network locations (like \\wibble\this\here.prg) in the code, but had the here.prg available in the exe as well. I only noticed it when I changed to a dial-up internet connection and every time I ran the exe it connected to the internet. If I disabled the modem, the program sat for a minute and then carried on regardless...perhaps you have a similar case there, where VFP is looking in a non-existant (but time-consuming) location first, before examining the other path locations.

>I wouldn't believe this one if I hadn't seen it myself.
>
>
>We have a VFP app with a rather larger and busy form (4 tabs, dozens of controls on each tab). It loads fine in our client's production area...takes about 1-2 seconds to load.
>
>When our client runs the same app in their test environment, the form takes 2 minutes to load. I've determined that the delay is between the form LOAD and the form INIT. We have very very little method code in the INIT event of individual controls.
>
>We're desperately looking for differences between the client's production server and their test server....but I figured I'd ask this...are there any signficant 'spots' between form LOAD and form INIT that we might want to check? it's just amazing that the same form will load in 1-2 seconds on one server, and 2 minutes on another server [accessing a mirror of the database]. Both servers are huge in terms of memory, processor, etc.
>
>I also looked at what is available with eventtracking, but it didn't seem that what was offered with that would help us.
>
>I realize this isn't much to go on, but we're stumped. Any clues?
>
>Thanks,
>Kevin