Maybe something like this ? :
* Set the date field you are working on in the form to not autoselect and not tab stop, declare a component ID and make an on enter EEP that reads the component ID into a variable using getproperty * Put a date time picker variable field on the form for the variable you get and select recalc form variables in the object properties * Make an on click EEP that checks for any change to the variable in case the user tried to click out to another field * Put a second occurrence of the date field you are working on right after the date time picker in case the user tabs out of the date time picker and make an on enter EEP for this second occurrence that checks for any change * Reorder the tab order to make it all flow correctly * Hide things as need to avoid confusion. Just a suggestion that might help? Dave Fitts From: [email protected] [mailto:[email protected]] On Behalf Of Bill Downall Sent: Wednesday, December 18, 2013 11:19 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Help me brainstorm: DateTimePicker and eeps 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
