Somehow Quiting out of a Switch structure seems dangerous to me?? Ben Petersen
On 7 Feb 2003, at 17:11, [EMAIL PROTECTED] wrote: > In a message dated 2/7/2003 9:58:57 AM Eastern Standard Time, > [EMAIL PROTECTED] writes: > > > 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. > > > Thom, > > You're just stubborn <g> However there IS a way to do it <g> and still > use return in the command file you write. Use a calling file i.e. set > var vSel10000 = 99 > edit using Inventory > *(Switch vSel011 > case 1) > > Switch vSel10000 > Case 1 > cls > Run STOKENT1.WCM > Quit To Inventory.wcm > Break > Case 2 > cls > Run StokEd1.wcm > Quit to Inventory.wcm > Break > Break > Case 3 > Run STOCKDE1.wcm > Quit to Inventory.wcm > Break > > If you do the run of the command file, then the next line is a quit > to, you can make them as deep as you want, but still use a return at > the end of a command file. If you want the whole file, 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] >
