>Hi All,
>I keep two complete sets of VFP forms, prgs, etc. in two locations, one is on C: the other on L: (mapped network drive). I can set default to C:\ and run test.prg and the one on C:\ runs. I then set default to L:\ from the command window and run test.prg, hoping that the test.prg on L:\ will run, but it doesn't--test.prg on C:\ runs instead! Sometimes I can get the default to change by using the complete path; i.e. DO L:\test . From then on, DO test finds the correct one. Now, VFP is pointed to L:\. When I want to SET DEFA TO C:\, the same problem occurs. CD, SYS(5), & SYS(2003) all show that default drive/dir is correct, but DO'ing a program from the command window runs the wrong one, namely the one that ran before changing default dir. Set default inside a .prg seems to behave correctly. This strange behavior seems to occur from the command window only.
>I hate to use the *bug* word here, but it shouldn't work that way, right? Does anyone else have this problem? Does SP3 fix it?

VFP will cache executable code in memory and trys to use it when the code in cache is at least as recent as the code you try to execute. Try issuing a CLEAR PROGRAM before switching to the other drive and launching the executable with the same name.

>TIA