DateTime Picker - Can't figure this out. [RESOLVED]

[The_Grudge]

I have a DateTime picker on my form that allows the user to select an "End Date" for how long a record should be written to the database. After having a tester run my program yesterday I was told I should not allow the user to enter an "End Date" that was earlier than the "Start Date". Makes sense.

So this morning I have coded the following.
The MsgBox displays when it should, and the date on the dtPicker changes to today's date, BUT the calander of the dtPicker is still open displaying the original date the user picked. How do I close the calendar part?
I thought the "REFRESH" statement would do it...but nope.
Or is there a better way to do this alltogether??

Private Sub dtEndDate_Change()
If dtEndDate.Value < MonthViewClinic.Value Then
   MsgBox "You cannot select an end date that occurs before the start date", vbInformation, "Invalid Selection"
   dtEndDate.Value = MonthViewClinic.Value
   
   dtEndDate.Year = Year(Now)
   dtEndDate.Month = Month(Now)
   dtEndDate.Day = Day(Now)
   dtEndDate.Refresh
   Exit Sub
End If
End Sub

[brucevde]

I don't know how to solve the calendar problem besides there are other problems you will encounter with your code.

For example, if MonthViewClinic.Value is Jun 1, 2005 and you click on May 31 you will get the error.

Invalid Property Value on the line
dtEndDate.Month = Month(Now)

I would just set DatePicker.MinDate property to the MonthViewClinic.Value instead. The user will never be able to select a date beyond the MinDate and will not be interrupted by annoying message boxes.

[space_monkey]

I have a form like yours here's what i did. And it seems to work.

Private Sub dtpfrmDateEnd_Change()
    If dtpfrmDateEnd.Value < dtpfrmdatebeg.Value Then
        MsgBox "You cannot select an end date that occurs before the start date", vbInformation
        dtpfrmDateEnd = Date
        dtpfrmDateEnd.Refresh
    End If
End Sub

I tried it without the refresh and it seemed to work that way too.

HTH

[Joacim Andersson]

I don't know exactly how your Form is designed but I personally never like programs that doesn't allow me to select whatever values I want, in whatever order I like. Meaning that you're actually forcing the user to select the start date before the end date. But what if after I've selected a valid end date I go back and change the start date to something later then the end date? Would that be acceptable? Of course it shouldn't but if you also restrict the user so they can't select a start date after the current value of the end date the user must learn that in some cases you must select an end date before the start date and in some cases you must do it the otherway around.

So what do you think, is that a good design? Wouldn't it be better to allow the user to select whatever he/she wants and do the validation before the Form is closed (or whatever you do before the settings kick in to action). Just a friendly suggestion.

[space_monkey]

That's a good suggestion, Joacim. I went back and changed that so that it occurs when the user clicks the "OK" button.

Private Sub cmdOK_Click()
If dtpfrmDateEnd.Value < dtpfrmdatebeg.Value Then
    MsgBox "You cannot select an end date that occurs before the start date", vbInformation
    dtpfrmDateEnd = Date
    dtpfrmDateEnd.Refresh
    Exit Sub
End If
setDate
bDateFlag = True
Unload Me
End Sub

Do you think this is a better design?

Thanks

[Joacim Andersson]

Much better, there are times where instant validation might be the best approach but in this case it's better to let the user fill in the values and check them before they are stored.

[The_Grudge]

Yeah, good call. I was working under the assumption that the user would do everything in Logical order. We all know that rarely happens!

[Joacim Andersson]

Well, most users would probably fill in the Form in logical order. But if you use your first approach I shouldn't be able to start by picking a start date that is later then the current setting of the End date, which in that case means that I need to set the end date first and then go back to set the start date. That's not logical is it?