I (just to be obnoxious) NEVER use QUIT TO in my work. The problem with quit to programming is that you cannot use the same subroutine in multiple circumstances.
An example is an application I support that is running both DOS and Windows, where a calculation routine is common to both sub applications, but for different end results. [EMAIL PROTECTED] wrote: >In a message dated 2/6/2003 11:51:05 AM Eastern Standard Time, >[EMAIL PROTECTED] writes: > >> >> �RUN cmdfile1.cmd >> � RUN cmdfile2.cmd >> � � � RUN cmdfile3.cmd >> � � � � � RUN cmdfile4.cmd >> � >> � >> �Any thoughts out there? > >Thom, > > Quit to cmdfile1.cmd > � �Quit To cmdfile2.cmd > � � � �Quit to cmdfile3.cmd > � � � � � �Quit to cmdfile4.cmd > � � � � � �From CmdFile4.cmd then > � � � � � �Quit to cmdfile3.cmd > � � � �Quit to cmdfile3.cmd > � �Quit to cmdfile2.cmd > Quit to cmdfile1.cmd > >I've actually done this 6 or 7 levels deep whill playing with stuff > >If you want a copy of a command file, I'll send you one. Let me know > >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] > > -- Albert Berry Full Time Consultant to PSD Solutions 350 West Hubbard, Suite 210 Chicago, IL 60610 312-828-9253 Ext. 32 __________________________________________________________________ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
