I have an application that will run a DOS command to move a file between 2 directories.

Sentence=Move f:\test\file1.txt f:\test2"

PCPerform Sentence

I use this command in a lot of my applications. This command will work on a Dos and Windows 98 workstation, but will not work from a NT4 Workstations.

If I substitute the MOVE command with the COPY command it will work. But I need to use the MOVE command. I have also tried using the SUSPEND command as well as calling a Batch file with the Move Parameters.

Paul,

Does the MOVE command work from NT's command prompt (cmd.exe)? From NT DOS (command.com)? MOVE works here for both at service pack 5.

-Stephen

Some shell commands don't seem to work in NT. I don't know why, it could depend on ERRORLEVEL or something.

A workaround (usually) is to create a batch file such as:

moveit.bat

move %1 %2 %3

and put is somewhere in your path, then just change your PCPERFORM to "moveit f:\dir1\xxx.txt f:\dir2\"

Warren. I tried your suggestion. No Luck. I am using service pack 6.

Stephen. I have not a problem with the Move command from the dos prompt. I can do this by starting a dos session or by using PCPERFORM or SUSPEND. It will always work from the dos prompt. It will not work when I am calling MOVE command or if I am calling a Batch file with the MOVE command directly from PCPERFORM or SUSPEND. If I replace the MOVE command with COPY there is no problem. I have tried this on several NT stations with the same result.

This may sound daft, but try

c:\command /c move c:\path1\filename1 d:\path2\filename2

at the command prompt, HELP MOVE should reveal some text.

Also exclude the possibility you have multiple command.coms

present using

dir c:\command.com /s /p

Steve

Very late response but we just got through this one. Determined if we

structured our DOS Move as follows, it worked.

PC Cmd.Exe Move etc, etc…

Now we can't get Arev's DirList() to work on NT. gggrrrr

View this thread on the forum...