Bill,

I don't have an absolute answer. But is has to do with command.com vs cmd.exe and the PIF file that VFP is using. I can get you more information on Monday

>I have an app that interacts with a DOS app that requires me to execute DOS batch files. The O/S is Windows NT 4.0 Workstation. Ususally, these have worked fine. I simply use
>
>cCmdLine = "\postmgr\dclbat 01 18 01-18"
>RUN &cCmdLine
>
>(the 01 18 01-18 are parameters for the DOS batch file, dclbat.bat)
>
>Recently, one client tried installing Partion Magic, ran into problems, and re-installed the O/S. Now, everytime this and other RUN commands for DOS batch files are run, I get a VFP error
>
>'Invalid Path of Filename'
>
>The file names and paths have not changed. The batch files run fine from the CMD command, but not within my VFP (6.0) app.
>
>At first, I thought it might be the FILE setting in CONFIG.NT, but I upped this to 100 (it was 20) but it didn't help.