Precisely Speaking
February 08, 2012, 01:56:33 AM
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
: So what's news with you? Tell us about it in "Getting To Know You"!
Home
Help
Calendar
Login
Register
Precisely Speaking
>
Training and Education
>
SB+ Programming Questions
>
Warnings for Mandatory Fields
Pages: [
1
]
Go Down
« previous
next »
Print
Author
Topic: Warnings for Mandatory Fields (Read 975 times)
Tom Pellitieri
Rock Star
Posts: 166
Tom Pellitieri - Toledo, Ohio
Warnings for Mandatory Fields
«
on:
August 23, 2010, 08:16:17 AM »
Is there any way to get SB+ to provide a warning that a field is mandatory when you press F2?
I have a secondary screen linked to a function key (PD.I, Options=S) where the first field is mandatory. If the field loses focus, I get the usual "mandatory" warning. If I press F2 without entering a value, the screen just stays on the field.
Effectively, when I press F2 it appears that nothing has happened, and that the screen is somehow "hung up". I tried putting a test to display a warning in the Process After Screen Accept (PASA) slot, but nothing appears.
Any suggestions??
--Tom
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
Posts: 1524
Re: Warnings for Mandatory Fields
«
Reply #1 on:
August 23, 2010, 08:19:09 AM »
That's the way mandatory prompts work, unfortunately. If you make it non-mandatory then you can use a process on the Proc After Screen Accept to check your mandatory prompts and handle them however you prefer.
Logged
-Kevin
Accidents "happen"; success, however, is planned and executed.
Tom Pellitieri
Rock Star
Posts: 166
Tom Pellitieri - Toledo, Ohio
Re: Warnings for Mandatory Fields
«
Reply #2 on:
August 23, 2010, 08:25:27 AM »
Well.. at least it works... just seems awkward that SB+ wouldn't provide the "Mandatory" warning after screen accept.
--Tom
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
Posts: 1524
Re: Warnings for Mandatory Fields
«
Reply #3 on:
August 23, 2010, 08:44:27 AM »
Far be it for me to defend SB+, but I think the rationale was to try to make it easier for programmers to check for mandatory fields rather than having to code for it each time. And because the baked in mandatory can be disabled, we geek-types can have it either way. It does seem like a good idea to display a message rather than just beeping and going to the field tho...
Might be something to post to the Better-and-Better board on u2ug?
Logged
-Kevin
Accidents "happen"; success, however, is planned and executed.
Pages: [
1
]
Go Up
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
General Category
-----------------------------
=> Getting To Know You
=> Announcements
=> Big Thoughts / Cool Ideas
=> Rants & Raves
-----------------------------
Application Support
-----------------------------
=> Red Leaf
=> Activant/Prelude Support
=> Summit Support
=> Avante Support
=> PRC Support
-----------------------------
Training and Education
-----------------------------
=> Connect!
=> U2 Programming Questions
=> SB+ Programming Questions
=> Web Programming Questions
=> Business Intelligence / MITS
=> PC / Hardware / Miscellaneous Support
Loading...