Lee, You can place the TRACE command in your code and then run it, and when it hits the trace command, it will start tracing. If you are already in trace mode, it will complain, but everything works.
I usually use the command DEBUG TRACE so it does not effect other people and when you forget to take it out, it won't cause any problems. To use the DEBUG command, before you run your program, you need to: R> SET DEBUG ON and turn it off when you are done. Troy -------------- Original Message Hello Everyone- I often write nested command files, and during the debugging process only need to trace the fourth or fifth program in the series, leaving the others alone. So as to avoid going thru all of the command files using trace, to get to the one that I need to debug, I use a couple of endif statements in a row, causing the code to drop me to the R>, at which time I remove the two endif's and strictly run the command file that I need to run. This process is OK if the command file, in question, performs a given task, but is a little cumbersome if the command file causes different choices and outcomes to be made in the command file in question. Does R-Base already have this ability? Is it possible to turn the debug on in the middle of a command file, and turn it off a few code lines later? Lee Bailey Bailey & Associates E-Mail: [EMAIL PROTECTED] Phone: 954-659-1780 Fax: 954-659-1781
