Dependent comboboxes and date picker

[edmscan]

Re: https://www.accessforums.net/forms/o...ges-41573.html I want a similar thing .. I have a listbox, and 2 dates (start date and end date) on the bottom of the form. When I select a start date from the datepicker (just easier than forcing a manual entry of the date) .. I want to reformat the start date textbox as yyyy/mm/dd and make the end date 6 days in the future from the start date. I could never find anything that would fire when I selected a date from the picker. I finally ended up using a button which I put my format code in .. and to change the end date and finally requery the listbox which uses those 2 dates. It works .. but I agree, there should be something that fires when the date is selected from the picker. These are all unbound controls. If anyone comes up with something I would be interested.

[Missinglinq]

Unlike many previous ActiveX DatePickers and Form-based calendars, Access does consider the Control to be physically populated when done thru this native DatePicker, meaning that all of the Control's associated events, such as the BeforeUpdate event, AfterUpdate event, etc, will fire.

A Control's AfterUpdate event doesn't fire until you leave the Control, but you can put your code in this event, then use code to force the Focus elsewhere, which will make AfterUpdate fire:


Move to another Control

Private Sub DateField_Change()
  AnotherControl.SetFocus
End Sub

You'll need to replace DateField and AnotherControl with names of your actual Controls.

Linq ;0)>

[ItsMe]

Using the intrinsic date picker to select a date and then format it as you wish will be problematic because the user will need to see the American date format (textbox control associated with the picker) in order for the date picker to work.

Using a series of comboboxes, one for the year, one for the month, and one for the date; will probably be the best solution.

[Missinglinq]

Using the intrinsic date picker to select a date and then format it as you wish will be problematic because the user will need to see the American date format (textbox control associated with the picker) in order for the date picker to work.

I don't follow; the user will only see a calendar! The Date Format doesn't really come into using the DatePicker.

Linq ;0)>

[ItsMe]

OP wants to do the following....
"... I want to reformat the start date textbox as yyyy/mm/dd and make the end date 6 days in..."

So I am imagining the need for an expression somewhere. I am also imagining the control associated with the date picker being visible in order for the intrinsic date picker to be used. The fact that the control associated with the date picker is visible will cause confusion for the User.

Now that I am posting this.... I suppose you could have an unbound textbox control on top of the date picker (to the side of the picker and on top of the control). But then back to the original issue of firing the expression after the date picker is clicked.