On occasion, I have an app that when I run the .cmd file at the R> all works perfectly, then I compile the very same .cmd with no changes and it does not work. Normally these apps run via the scheduler and do not have any screen input or display, i.e. data compiling routines such as with EDI transactions. I run the cmd through trace and all shows OK, but then again it runs OK at the R>.
I am looking for suggestions on methods others use to debug the program after it is compiled into an exe. Remember, there are no user inputs or screen displays on this particular app, which is normal for my scheduled programs running data routines. Thanks, -Bob -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441
