Re: [U2] SB Client - Disable TAB
Hi group, At our side, we solve these problem with a system wide "validation" process defined on all SBfields which check if mandatory fields sequentially defined "before" the current field are empty. If one is found it output a error message and exit with @RTN.FLAG = {mandatoryfield} else it execute the validation expression for the current field. I'm ok with you, this is a trick that SB+ can do. My two pence. Manu *-- For info : @MAINFILE is the current datafile @LINE<1,18> is the current fieldname @LINE<1,1> is the current AMC value ; if negative this is a @WORK field (ABS(@LINE<1,1>) is the AMC of @WORK @CNT the current mv value @PROC.NAME is the process names ... check 1,2,3,... until you found Readv XXPROCESS<1> = 'I' ; this is the input-process-defn Read PROC.DEFN then PROC.DEFN<5> is the DICT.FILE where 'INPUT.DEFN' reside PROC.DEFN<6> is the DICT.FILE KEY of input.defn of the current screen Read INPUT.DEFN FROM 'DICT ': PROC.DEFN<5>, PROC.DEFN<6> Then LOCATE(@LINE<1,18>,INPUT.DEFN,15;POS) Then check all field sequentially "before" the current FOR I = 1 TO RG -1 IF INPUT.DEFN<22,I> = 'Y' THEN Read field.defn from DICT.FILE,INUT.DEFN<15,I> If field.defn<2,1> < 0 then check @WORK else check @RECORD IF field.defn<2,2> < 0 then mv'ed else am'ed Then check if the value is empty or not If yes, output a error, rtn.flag = INPUT.DEFN<15,I> END NEXT I > -Message d'origine- > De : u2-users-boun...@listserver.u2ug.org [mailto:u2-users- > boun...@listserver.u2ug.org] De la part de Israel, John R. > Envoyé : vendredi 24 septembre 2010 21:04 > À : u2-users@listserver.u2ug.org > Objet : [U2] SB Client - Disable TAB > > This may be old news to most folks, but we have found that if a user > navigates through a GUI SB+ screen and uses their mouse to click on an > input, none of the logic tied to the prior inputs are run. This includes > being able to skip right past mandatory fields. > > For example, a screen has 5 required inputs followed by 5 non-required > inputs. If the user is in input 2 and uses their mouse to click into > input 8, SB allows this to happen and the required fields and any > associated logic tied to inputs 2 through 7 are ignored. > > This appears to be a huge SB bug. Sure we could fix it for a specific > screen, but that does nothing for the hundreds (or thousands) of other > screens. > > Does anyone have a realistic solution to this condition? > > > > John Israel > Senior Programmer/Analyst > Dayton Superior Corporation > 1125 Byers Road > Miamisburg, OH 45342 > ___ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] SB Client - Disable TAB
John, what you've described is a feature of the GUI; the ability to click through prompts in any order. If there are mandatory fields you shouldn't be able to save the record until those fields have a value, but if those fields are not mandatory the validation may never run. This can, of course, create some madness when you have a validation process or PA on a field that is setting up stuff for something to follow later. The short answer, though not a good one, is "don't do that". In GUI each prompt has to be considered completely standalone knowing that anyone can click to it from anywhere. It's a completely different programming paradigm than what we have historically done with green screens. Oh, and it happens in character mode as well when the mouse is used to click through to fields. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] SB Client - Disable TAB
What are your typical screen settings? Your SB+ version? Is the "Write Record" flag set or do you do your own write? Are the fields in @RECORD or @WORK. In our screens at least, as long as the field is set to "Mandatory" and is a @RECORD field, and the write flag is "Y", it takes the user back to the first unset mandatory field if they try to save the record. "mandatory" does not mean the same thing as having a validation on the field that checks for a valid value. Those validations would get skipped if they didn't visit the field. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Friday, September 24, 2010 3:21 PM To: 'U2 Users List' Subject: Re: [U2] SB Client - Disable TAB Yeah, we could do that on a screen by screen basis, but that does not solve the overall problem. This is true in EVERY screen. The one screen that we found this on will be altered to do lots of additional tests to ensure the all required fields get filled properly. The fact that we are just now discovering this means that we do not have this issue very often, but it does appear to be a flaw. John Israel Senior Programmer/Analyst Dayton Superior Corporation 1125 Byers Road Miamisburg, OH 45342 -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Davis Sent: Friday, September 24, 2010 3:12 PM To: U2 Users List Subject: Re: [U2] SB Client - Disable TAB I think this is more of an issue with @WORK fields than @RECORD fields. In any case, perform a validation after screen accept if it's important. If it's important that the user not enter a field until other fields "before" it have been entered, bounce them out by using the process before field slot. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Friday, September 24, 2010 3:04 PM To: 'u2-users@listserver.u2ug.org' Subject: [U2] SB Client - Disable TAB This may be old news to most folks, but we have found that if a user navigates through a GUI SB+ screen and uses their mouse to click on an input, none of the logic tied to the prior inputs are run. This includes being able to skip right past mandatory fields. For example, a screen has 5 required inputs followed by 5 non-required inputs. If the user is in input 2 and uses their mouse to click into input 8, SB allows this to happen and the required fields and any associated logic tied to inputs 2 through 7 are ignored. This appears to be a huge SB bug. Sure we could fix it for a specific screen, but that does nothing for the hundreds (or thousands) of other screens. Does anyone have a realistic solution to this condition? John Israel Senior Programmer/Analyst Dayton Superior Corporation 1125 Byers Road Miamisburg, OH 45342 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Dave Davis Team Lead, R&D P: 614-875-4910 x108 F: 614-875-4088 E: dda...@harriscomputer.com [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif] 6110 Enterprise Parkway Grove City, OH 43123 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Dave Davis Team Lead, R&D P: 614-875-4910 x108 F: 614-875-4088 E: dda...@harriscomputer.com [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif] 6110 Enterprise Parkway Grove City, OH 43123 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not a
Re: [U2] SB Client - Disable TAB
Yeah, we could do that on a screen by screen basis, but that does not solve the overall problem. This is true in EVERY screen. The one screen that we found this on will be altered to do lots of additional tests to ensure the all required fields get filled properly. The fact that we are just now discovering this means that we do not have this issue very often, but it does appear to be a flaw. John Israel Senior Programmer/Analyst Dayton Superior Corporation 1125 Byers Road Miamisburg, OH 45342 -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Davis Sent: Friday, September 24, 2010 3:12 PM To: U2 Users List Subject: Re: [U2] SB Client - Disable TAB I think this is more of an issue with @WORK fields than @RECORD fields. In any case, perform a validation after screen accept if it's important. If it's important that the user not enter a field until other fields "before" it have been entered, bounce them out by using the process before field slot. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Friday, September 24, 2010 3:04 PM To: 'u2-users@listserver.u2ug.org' Subject: [U2] SB Client - Disable TAB This may be old news to most folks, but we have found that if a user navigates through a GUI SB+ screen and uses their mouse to click on an input, none of the logic tied to the prior inputs are run. This includes being able to skip right past mandatory fields. For example, a screen has 5 required inputs followed by 5 non-required inputs. If the user is in input 2 and uses their mouse to click into input 8, SB allows this to happen and the required fields and any associated logic tied to inputs 2 through 7 are ignored. This appears to be a huge SB bug. Sure we could fix it for a specific screen, but that does nothing for the hundreds (or thousands) of other screens. Does anyone have a realistic solution to this condition? John Israel Senior Programmer/Analyst Dayton Superior Corporation 1125 Byers Road Miamisburg, OH 45342 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Dave Davis Team Lead, R&D P: 614-875-4910 x108 F: 614-875-4088 E: dda...@harriscomputer.com [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif] 6110 Enterprise Parkway Grove City, OH 43123 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] SB Client - Disable TAB
I think this is more of an issue with @WORK fields than @RECORD fields. In any case, perform a validation after screen accept if it's important. If it's important that the user not enter a field until other fields "before" it have been entered, bounce them out by using the process before field slot. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Friday, September 24, 2010 3:04 PM To: 'u2-users@listserver.u2ug.org' Subject: [U2] SB Client - Disable TAB This may be old news to most folks, but we have found that if a user navigates through a GUI SB+ screen and uses their mouse to click on an input, none of the logic tied to the prior inputs are run. This includes being able to skip right past mandatory fields. For example, a screen has 5 required inputs followed by 5 non-required inputs. If the user is in input 2 and uses their mouse to click into input 8, SB allows this to happen and the required fields and any associated logic tied to inputs 2 through 7 are ignored. This appears to be a huge SB bug. Sure we could fix it for a specific screen, but that does nothing for the hundreds (or thousands) of other screens. Does anyone have a realistic solution to this condition? John Israel Senior Programmer/Analyst Dayton Superior Corporation 1125 Byers Road Miamisburg, OH 45342 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users Dave Davis Team Lead, R&D P: 614-875-4910 x108 F: 614-875-4088 E: dda...@harriscomputer.com [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif] 6110 Enterprise Parkway Grove City, OH 43123 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users