>Hi Dave,
>>it'll find the one previously compiled into another .app file which may have been run earlier rather than from the .fxp on disk.
>
>I believe I wrote you about some of the problems with the search sequence in VFP compared to what you are used to in FPW. I've found only 2 ways of reliably working with identical named functions / programs in different App's:
>Either rename via home-grown source analysis
>Or implement a calling hierarchy from the programs in the stack.
>
>If VFP is supposed to search, it can find routines in *any* App before finding the prg. Since there is no search method described, you can't call it a bug, but it breaks backward compatibility. It is hinnted at in the VFP docs...
>
>But in your case: can't you recompile the app ?
>
>HTH
>
>thomes

Yes but it was knowing it was in the app in the first place. We have 30 or so .apps associated with the main project. I didn't think it was a bug. As I said to others it would be nice if the debugger could identify the source file that contains the out of date file.