In a message dated 3/17/2002 11:22:04 PM Eastern Standard Time, [EMAIL PROTECTED] writes:
<< So "Save the Quit-To" !!! >> I'm not sure if quit to counts as a kludge or not, but I can say it has saved me a LOT of hassles since I started using it. I'm using it slightly differently than it was originally explained to me, but it works. When I use the to run the program, I use a common command file that just has a series of case statements then a run, then quit to the calling file, such as: Case 1 run (command file name) quit to calling command file break Case 2 run (command file name) quit to calling command file Break Etc, etc, As I understand it, it was supposed to be a quit to at the end of every command file. This is a lot quicker, and doesn't seem to cause any problems. This method keeps all of my OLD command files with a return at the end of the file working with no changes, and is independent of what ever command file calls it. It allows me to use a common command file as a menu system, and I only need to maintain one command file for each menu system. By creating a generic menu program, a global search and replace for the quit to, and I can have it running in just a few minutes. Just my $.02 worth 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/
