John W Colby
jwcolby at gmail.com
Mon Mar 16 09:46:09 CDT 2009
I use a class to handle this. There is a calendar control that comes with Access, or at least can be found. It is then placed on a form and under normal (non-class) conditions the control's events are hooked right in the form. I create a class to handle this but also to handle the interface between the calendar and the object needing the calendar. My objective was to pass in a reference to the control which you want the data placed into, i.e. the text box on the form. The class then stores a pointer to this control, and when the user clicks on a date the selected date is placed into the object passed in. I thought I had a demo on my site (back when my site was functional). I will look and see if I still have the demo. John W. Colby www.ColbyConsulting.com Arthur Fuller wrote: > JWC et. al. > > It would seem that a good candidate for the collection of control classes > would be a date control that automatically includes a pop-up calendar with a > little icon that appears in the OnEnter event, so that the user may either > type in the date value or click on the icon to open the calendar control. > > Coding that functionality the old way is not that difficult, but it seems a > better idea to do it just once and "inherit" the functionality in every date > control throughout the application. > > Arthur >