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] **********************************************************************
