-
All of you probably know that the maskedit control ain't the best for handling dates. That only leaves me one choice: the vb6 datepicker.
Are everyone using the datepicker or am I missing something? The datepicker's value CAN'T be set to NULL (unless you want the control to have a checkbox in it and the NULL value is simply grayed).
What's the solution to this? Let's imagine you have a form with a customer's informations, including his DOB. Using a datepicker would NEED a default DOB. You will all agree that this MUST be avoided.
Thank for your time...
-
If the datepicker's not bound, it's not that big of deal. You set the date value for a DOB to some early value (0, for instance) and then check before updating the database if the value is 0, changing it to null.
-
The problems is, to set the datepicker to null, you need that checkbox in the control. Which is ugly and unlike all my other controls.
Also, when using that checkbox, and setting the value to NULL, the date doesn't disappear - it only goes gray. I want it to disappear.
These 2 facts makes me believe I need another control. But I don't know which, since the maskedit will be much worse.
