I believe Arev uses it's own version of the command line when using the execute and pcperform commands or when shelling out from the TCL window. This really causes problems when trying to use command line commands or .bat files which use Windows long file names. I think I remember hearing about a way to specify in Arev which command line version you want to use, such as the Windows XP command line which recognizes long file names. I can't remember how it's done. Is this possible? Thanks.

Use cmd.exe vs command.com. Change your _default.pif etc to use cmd.exe

I'll try that, thanks.

even using cmd.exe /c syntax you may want to start with creating temporary bat files

since long file names are allowed you may exceed the 150 characters (or whatever it is) for the maximum length of the dos command out of Arev

I have a process that does a conversion from Arev to HTML format of thousands of records. Various commands, including creating directories, removing them, renaming files, gzipping them, etc. are all done through batch commands.

The batch commands all terminate with two exit commands. Why two? Because sometimes the first one doesn't take for whatever reason. Even still, sometimes a batch session remains stranded, using up its own tab on the Windows quicklaunch toolbar. Typing EXIT terminates the window.

This stranded window happens perhaps one in every 25,000 commands (maybe even higher). Batches occur 10,000 cases at a time, and a batch of cases is as likely as not to run into this problem. Does anybody have a clue why this is happening and what I might be able to do to get around the problem? We don't get bad data or anything, and processing does not get hung up. It's just annoying to have to periodically terminate windows that we shouldn't have to.

View this thread on the forum...