This Topic is AREV 3.111 - but I am hoping someone now working in OI might know the answer to this.

I have always thought that doing anything via a 'SUSPEND' operation is a linear operation which would be concluded before control goes back to AREV.

Just today I have found a major flaw or error occurring and I am in despereate need of a fix.

I hope someone out there has seen something like this before and if not please give it a try yourself, perhaps its a Computer configuration problem that I have rather than a bug in the 'SUSPEND' operation.

Here we Go::::

As you may know certain DOS commands do not work anymore in regular dos becuase of Win2000/XP.

Therefore we have to use CMD /C START inorder for there DOS commands to work.

COMMAND:

perform "SUSPEND EXIT CMD /C START F:\MOVE.BAT FROM-A TO-B"

BATCHFILE-MOVE.BAT

MOVE %1 %2

EXIT

PROBLEM:

The command is executing properly but it looks like control is going back to the AREV system before the file is moved and the next AREV commands are being skipped. The system is actually skipping over compiled AREV codeing.

The only way I discovered this was by putting a DEBUG into the program right after the MOVE, then the program stops at the DEBUG and executes the following AREV code in proper sequence.

Terry,

It is doing exactly what you told it to do although clearly not what you intended. Using the Start syntax you are telling Windows to go ahead and launch another process. Once the start command is initiated control returns immediately back to AREV. You need to run the command without using the start syntax but rather run the batch file directly from AREV or use the cmd /c batchfile. But definitely don't use the start command.

HTH,

John

Terry,

If you must use the start command, there is a /WAIT parameter that I think will make Arev wait for your command to finish. Type START /? at a cmd prompt to see the syntax.

View this thread on the Works forum...