>>><snip>
>>>>>>If you build your .EXE from a network share, and that particular share is not available at runtime (IE, your .EXE runs on an entirely different network), you'll have to wait for VFP to "timeout" before it'll even load your app and start executing. SYS(2450) will eliminate that check so it doesn't have to wait.
>>>>>
>>>>>
>>>>>Hi Fred. If I build on a local D drive and run on a user machine which has only a C drive what effect will this have and should I use SYS(2450)?
>>>>
>>>>I'm not sure if if local drives do the same thing. And even if they do, the timeout probably isn't as long as occurs for a network share.
>>>
>>>Would you recommend the use of SYS(2450,1) as a default since if the file is not found within the exe the path will be searched anyway? iow, isnt it better/faster to first search the exe as a default?
>>
>>I would think so. Unless you have specific needs to let VFP do the searching, looking in the EXE first would seem to be the better way to go in all cases.
>
>Thanks Fred.

I think they kept it working the same way it was so that older programs re-compiled in newer versions of VFP wouldn't mysteriously break with things not being found if they changed the default searching. Hence the new SYS() command to give you control.