How about a stored procedure ON CLICK? Razzak's idea is probably better,
though.
Albert
On 12/18/2013 11:00 AM, Bill Downall wrote:
Albert,
A trigger would work for the checking, but the problem is how to
trigger the trigger upon changing data in the field.
Bill
On Wed, Dec 18, 2013 at 12:45 PM, Albert Berry <[email protected]
<mailto:[email protected]>> wrote:
Bill, could you perhaps create a trigger with the checks in it?
I'm thinking something like
- Get the new value
- Get the PK of the row
- Get the old value and whatever else you need to know
- do the valid/invalid change checks
- abort trigger or let it run
- in the trigger if the change is aborted, quick note to user and
return to the picker
Albert
On 12/18/2013 9:19 AM, Bill Downall wrote:
Hi, all,
I'm needing a strategy that I'll bet some of you have solved.
I want to do some date checking whenever a user makes a change
to a date.
Unlike text-based controls, a DateTimePicker does not have an
"on Exit" eep. Mousy users might not move to the "next" field
on the form, but could jump anywhere. They could even close
the form while the cursor is still on the date field.
The on-click/ and on-double-click eeps trigger before they
make the change I care about.
Table eeps: on leave section, on row exit, are too late to
check and pop-up necessary dialogs for users.
What would you do? Thanks.
Bill
