>Hi,
>
>I'm still plugging away at the VFP8 beta to see if I can get my app up and running. I've posted before about this same subject, but I've done some digging and so have a bit more information (I'm always guilty of not doing this, and it's not really fair on other users!)
>
>I've got a project which contains code like
>
>SET PROC TO programname
>DO programname
>
>(I only use quotes in the following case)
>
>DO "program name.prg"
>
>And on running my app I get the error
>
>Invalid path or file name
>
>Now I then typed the fullpath in the command window to execute the program, skiped the line of code in the debugger, and guess what, it works...
>
>I've compared my paths (default/search paths) to my VFP6 project and they are identical. I don't use search paths in my VFP6 project. So I'm wondering if the behavior of VFP8 beta is different in this respect. I have a nasty feeling it may be down to configuration of VFP8 to create the same type of environment, but it has proved to be quite puzzling. Does VFP8 handle program names differently in code in VFP8, or have I overlooked something that maybe my lack of experience may have caused?
>
>Sorry to repeat any previous threads, but with more information, I guess it can be of benefit to others when adding a little more specific information. Any feedback appreciated as I'm desperate to test the new features of VFP8 in my existing application!!

Simon,
I couldn't reproduce what you're saying. Search paths are working as they should (VFP6,7 and 8).
What I noticed in your message is error message "Invalid path or file name". If programname was not found I expected a message like "File ... not found".
Only way I can get that message was having an invalid path either search path or command itself. ie:

do "c\:myprog" && Invalid path or filename

*Search path in tools\options\file locations
data;c\:myprog

do NonExistentProg && Doesn't exist so VFP attempts to use search path
&& which is invalid

Or :
do ExistingProg && Again invalid path or filename
because VFP didn't get the extension so should check in search path again for precedence.
do ExistingProg.prg && Would work provided "ExistingProg.fxp" is in default dir.

Cetin