Bob, I have taken a different approach to this. I don't use a compiled application for automated tasks. I have a full version of R:Base installed on the server. I create an RMD file in the RBase directory. I create a bat file in the root directory which calls the RMD. I create a scheduled task to call the the bat file and make sure that the appropriate permissions are assigned to the task. Now if problems occur (the usual one is forgetting to SET ERROR MESSAGE 2059 OFF when no rows are found) I just pull up a simple text editor and make the changes needed and we are back in business.
Hope it helps. Jan ----- Original Message ----- From: [EMAIL PROTECTED] To: RBASE-L Mailing List Sent: Thursday, June 12, 2008 6:12 AM Subject: [RBASE-L] - Debugging Compiled Apps 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
