sorry, i mistyped. The batch file does NOT contain the cmd.exe reference only the copy command. I have looked at the OS - it *is* 32 bit windows 7. There is only one copy of copy.exe.
I am giving up on this line of inquiry. It appears to me that there is something fundamentally broken with LEP and v13.5. The batch file works as expected from the command line, & from the explorer interface (i.e. double click), but fails from LEP; and so far NOTHING has made the slightest bit of difference in getting the batch file to function as expected when called from LEP. The batch file does appear to be executed - as in an error file (empty) is generated when requested by the batch file. I started down this (endless it seems) rabbit hole by trying to execute the xcopy command directly from LEP - but that failed as well, even when the exact same command was given to the command line. So.. 2 different approaches to get the same functionality, using xcopy, with no functional result. Something in LEP is broken (at least in regards to this specific command). I do not know what, I can not change it, 4D will not change it now. I am moving on to a different means of attempting to accomplish the same task. On Thu, 9 Nov 2017 00:07:48 -0500, Chip Scheide via 4D_Tech wrote: > no Ill try that too > Thanks > >> Chip, >> >> have you tried to change the .bat file to eliminate the ‘cmd’ call >> and run xcopy directly, so that .bat would read just: >> "xcopy <source_path> <destination_path> 2>> <Error_file_path>” >> >> And then call the .bat directly in your LEP statement? >> >> Why do you need that “cmd.exe” for? >> >> julio >> ' >>> On Nov 8, 2017, at 10:06 PM, Chip Scheide via 4D_Tech >>> <[email protected]> wrote: >>> >>> >>> what is in the batch file is : >>> cmd.exe /C xcopy <source_path> <destination_path> 2>> <Error_file_path> >>> >>> All paths are valid. >>> when I execute the batch file from the OS (double click, or command >>> line) it works, and does NOT create an error file. >>> When run from LEP it does nothing, and creates an empty error file. >>> >>> I will have to check, but I am mostly sure that the windows OS (7) >>> is 32 bit >>> >>>> On 9 Nov 2017, at 4:44 am, Chip Scheide via 4D_Tech >>>> <[email protected]> wrote: >>>>> >>>>> I have tried all of the offered suggestions: >>>>> Start ?b >>>>> running without a call to cmd >>>>> \batchfilename\ >>>>> extended this to cover the file paths in the batch file >>>>> >>>>> none of these result in file copying when started with LEP. >>>>> HOWEVER the batch file contains a redirect of stderr to a disk file, >>>>> when run though LEP the error file is created. >>>>> The error file is empty... but it is created. >>>>> SO.. LEP is actually executing the batch file, just not doing anything. >>>>> >>>>> any more ideas?? >>>> >> >> -- >> Julio Carneiro >> [email protected] >> >> >> >> ********************************************************************** >> 4D Internet Users Group (4D iNUG) >> FAQ: http://lists.4d.com/faqnug.html >> Archive: http://lists.4d.com/archives.html >> Options: http://lists.4d.com/mailman/options/4d_tech >> Unsub: mailto:[email protected] >> ********************************************************************** > ------------ > Hell is other people > Jean-Paul Sartre > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
