|
|
Question : Forms6i Q: Getting around validation behaviour
|
|
Hi all, here is the scenario: Oracle 8i DB on Unix. Forms 6i on Win2K. Client server environment.
I have a form with various text items -- date fields, number and char.
As you all know, when I enter a non numeric into a number field or a non date into a date field and tab off the item, I get internal validation firing resulting in a validation error (and message).
If instead of tabbing, I click on a button, the validation fires and produces an error message. Then my button fires and produces a message (based on the fact there is invalid data in the item) and then validation fires again for that item giving a third error message.
On screen, this looks crappy. I want the validation message to appear only once, and the WBP trigger code only to fire if the data in the fields are valid.
Given that users will enter bad data, and they will use the mouse (instead of tabbing), how can I avoid the multiple error message problem, providing a single message?
(Note: I've tried combinations of the following possibilities: using ENTER; to force validation. using FORM_SUCCESS to check form success checking get_item_property ('item_name',ITEM_IS_VALID).
I thank you all in advance, Regards, JT
|
Answer : Forms6i Q: Getting around validation behaviour
|
|
@markgeer&venkotch You got me wrong: I assume that Mouse Navigate IS set to No - otherwise the WBP won't fire because the navigation out of the Text Item failed!
I agree: Setting Mouse Navigate to No is USUALLY right, but in some circumstances it leads to unpredictable results if your WBP-trigger is sensitive to the cursor position.
|
|
|
|
|