>>I'm confused about Sys(2450).
>>
>>I thought that VFP always searched the current executing module (FXP file) plus all "Set Procedure To" entities before looking to disk to find a function/procedure by a given name. i.e., so that if you had a FXP with multiple procedures in it, and one procedure in the FXP called another procedure PROC2 in the same FXP, then VFP would _always_ preferentially find PROC2 in the FXP and execute it, before looking for and executing a PROC2.FXP that might be on disk.
>>
>
>The issue is that even when the routine VFP ends up executing is bound into an APP/EXE, the search order means that VFP can go off and search the disk before settling on the bound routine. SYS(2450) lets you turn off that behavior so that you don't spend the time for the search. It doesn't change what gets executed, only how long it takes.
>

I'm still confused. VFP help says the default behavior is this:
"Search along path and default locations before searching in the application."

But I thought that VFP always searched inside the current executing module (FXP file) plus all "Set Procedure To" entities before looking to disk to resolve a UDF reference or a "DO PROCNAME" reference. If this is the case, then how does it speed things up to assert SYS(2450,1)? In other words, that's how VFP already works, so what VFP Help says here about SYS(2450,0) is NOT the default behavior (or is it?). Have I been wrong about this all along?