If your environment has promoted a consistent interface across all programs,
then congratulations on the {} and <> prompting.Unfortunately within all of my client's systems, there rarely appears a consistent interface, thus my perspective on this topic. Even within one set of programs from the same menu, some prompts for "Enter Company" use the automatic <enter> and some do not. Oddly enough, this example does a "R%3" to the answer so even if it is INPUT A,3 then the users either type "1"<enter> or "END" without. Doesn't paint a good picture. Also, part of my perspective is that virtually all of my client's systems are a strong mix of procs and programs and procs don't support the automatic <enter> (at least I haven't seen it). So that's another inconsistency that I deal with. Thanks Mark Johnson ----- Original Message ----- From: "Brutzman, Bill" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, May 06, 2008 10:15 AM Subject: RE: [U2] Press any k > It is handled via the prompts... using [square] brackets for standard > numbers of digits and <triangular> brackets for variable length entries. > For most users, this takes approx one day to get acclimated. > > InCorrect entries lead to an error screen with a Beep.Beep.And.Sleep. > > In all, this method is a fast way to validate entered data. > > --Bill > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of MAJ Programming > Sent: Tuesday, May 06, 2008 2:00 AM > To: [email protected] > Subject: Re: [U2] Press any k > > > That's the trouble. It CANNOT be used 'all over the place'. Surely you have > names and addresses who's lengths are often not their maximum. Even dates > can have today as 5/6 instead of 05/06/08. Money values also cannot be > dependent upon consistent lengths. > > Thus, even though every 6 digit PN can be consistent, that's only for one of > dozens of other entries which is my original point. The users would have to > memorize those that requre <enter> and those that don't. Plus, how can you > cause the errant <enter> for the answering following the INPUT PN,6 to NOT > welcome the <enter> alone. OR what if <enter> alone were a valid choice but > not the intended choice. > > It's hard to compare the savings of keystrokes to the 'back-up' concepts of > wrong following answers. > > So in this divided topic, I choose to always require a <enter> even if it's > a Y/N answer. > > Respectfully, > Mark Johnson > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
