I have a form in a booking system which contains a subform which is a replica of the old ActiveX calendar control that Access 2010 doesn’t have anymore. One particular use is to create a new booking. This means the form is “sitting” on a new record. However I don’t want that record written until I am sure that all the data is properly validated.
However I have a little Gotcha. If the user clicks on the calendar to select a new date, my master forms Before_Update event fires – indicating that Access is trying to save the forms contents. As I said I don’t want that to happen before I am ready. So I have added an unbound invisible checkbox to my form which is initialised to false. In the Before update event I check whether it is true or not and if it isn’t I CANCEL the update.
The problem is, this seems to prevent the Calendar subform from receiving some of its events. The days are represented by labels, and they fire. The bigger events like previous and next month are small buttons. They don’t fire at all.
I know that the Calendar works as it is used elsewhere in the application as a subform and in that place the events fire just fine.
So my question is. Is there a way to get this form/subform combination working so that I don’t end up creating a new record before I am ready.
This goes against the way access works by default. the only option I am aware of is to manually load and save your records, ie change all your textboxes etc to unbound in the oncurrent event manually populate the data in the textboxes. when you want to save copy the data from the textboxes back into invisible bound textboxes and mannualy save the record