[RBG7-L] - Re: Setting Default for Variable DatePickerLeaving NULL as Option

[David M. Blocker]

Emmitt   Thanks for clarifying. With the change Razzak announced today, I probably won't need this suggestion but it IS very slick!   David   David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: Emmitt Dove To: RBG7-L Mailing List Sent: Tuesday, August 17, 2004 12:20 PM Subject: [RBG7-L] - Re: Setting Default for Variable DatePickerLeaving NULL as Option David, The form has a calendar to which you assign a componentid.  The form has an on-after-start eep that sets the property visible for that componentid to 'false'.  In your context there would be no radio group - just a button that says "specify date".  The eep behind the button sets the property visible for the calendar to 'true'. Yes, you would still have to check to see if a date has been selected.  In your code that tests the date field for a value (not null) you would also need to look at a flag that you set in the eep behind the button to see if they intended to include a date and take the appropriate action if the flag is set but the date value null. In my form the variable radio group has four search methods.  Two of these involve dates, two do not.  I merely turn things on and off (visible true/false) depending on the method selected. I like your idea, Emmitt, but I�m not sure I follow completely.   What you do mean, �present a variable radio group for search method, then expose the components appropriate to the search. �  Could you give some details?     Even if I used your �specify date� button which has possibilities, the user could click on it, make the calendars visible, but then not actually click on them.  I need a firm way to know if they did or did NOT want to include dates in the search.    Right now, I plan on using Razzak�s enhancement to set default values in the calendars but NOT preset values before entering the form. This way if they don�t click on the calendar, the variable remains null and I know they did NOT click on it.  I suspect your way is better but I�m not quite understanding the details.   David David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: Emmitt Dove To: RBG7-L Mailing List Sent: Tuesday, August 17, 2004 7:52 AM Subject: [RBG7-L] - Re: Setting Default for Variable Date PickerLeaving NULL as Option David, I have a similar form where a user may or may not want to include a date range in a search - this actually uses two calendars.  When the form opens I hide the calendars and present a variable radio group for search method, then expose the components appropriate to the search.  In this way I know whether or not the date range is part of the search. How about a button on your form that says "specify date", and an eep that sets the visibility property on the calendar?  (Your on after start eep for the form would have previously set visible off ...) Aside:  your message apparently had some XML tags in it; could this be part of the faux spam problem? Hi R:Base buddies   Looking for some idea.  Here�s the situation:   I have several screens which prompt users for search criteria for reports, editing screens, etc. Several of these refer to a date field used in an invoices table: in this company, invoice dates are almost ALWAYS the 15th or 16th of the month.  My users have requested that these dates default to the 15th or 16th when the form comes up, instead of the current date as it does now.   Here�s the problem:  I�m using variable Date pickers for these fields.   The user is most cases is NOT required to include the date in the search criteria.  Now it works fine � even though a date shows in the picker, unless they click on it to change it, the variable actually is NULL when the user exits the form. ONLY if they click on it and change the date manually or by the calendar is the variable set to a date. So the calling program can check for the variable NULL or NOT NULL and build the where clause accordingly.  In fact, I actually have a message box on the form warning them that even the date showing is the one they want, they must click on the picker to actually select it.  (If you don�t, the variable remains NULL)   I know I can default the date picker to the 15th of the current month by actually SETTING the variable for the picker to that date prior to going into the form, but then how can I tell if the user actually WANTS that date used in the search?  It could be unchanged because they never clicked on the picker, and it could be unchanged because they clicked on it and WANT that date. There�s no way to tell that I know of.   The only idea I�ve had is a little kludgy: add a radio button: �Use date(s) in search criteria yes /  no� with no default set.  The form would have an error trap to force the user to indicate with a yes/no click if they want the date.  This way I can have a default and know if the user wants that date or is just ignoring it.   Is there a better way?  In my current release of R:DOCS, I don�t see a PROPERTY command that would set a default value for the picker, but leave the variable NULL until the user actually clicks on it to select it.  Since I know there a quite a few new options that aren�t yet in R:DOCS, is there one that will do what I want?   Or can anyone think of another way?   David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT  06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED] Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT  06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED]