In a message dated 3/18/2002 10:01:21 AM Eastern Standard Time, [EMAIL PROTECTED] writes:
<< CASE 1 Run Checkit.cmd Quit Checkit.cmd CASE 2 Run Printck.cmd Quit Printck.cmd Is this correct? >> Steve, I re-read the email, and the quit to should be to the calling program, not the command file your calling. If you want to quit to the cmd files, which is the way it was first explained to me, you have to put the quit to in the cmd file. As an example Quit To Checkit.cmd then at the end of the Checkit.cmd , instead of Return, you use Quit To the <Calling Program>.cmd and that returns you to the calling program. By using the Run Checkit.cmd Quit To Calling Program.cmd You can make the code a little more independent of where it is run. By using this method, I can place the code in any directory, call it using the run command, and then it quits right back to where I direct it in the calling program. The .cmd file runs with a simple run, can be debugged to return to the R> screen, and then when it all works, I just add the names to the calling program. The explanation is QUITE convoluted the way I explained it, but the code runs real smoothly <g> If you want some more examples, I can send you several pieces of code. If so, send me a quick email, and I'll send them to you Damon Damon D. Kaufman President Stalder Spring Works, Inc ISO-9002 / QS-9000 Certified 2345 S. Yellow Springs St. Springfield, Ohio 45506 Voice 937-322-6120 Fax 937-322-2126 email: [EMAIL PROTECTED] ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
