Max Wanadoo
max.wanadoo at gmail.com
Fri Mar 6 00:41:56 CST 2009
Ok, but surely at some stage the NEW record is going to be written-away. At this point it is no longer NEW and you can repopulate the combo box in the after update event with a flag to denote that it needs repopulating (to avoid it doing it unnecessary each time a record is updated) Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: 05 March 2009 20:52 To: Access Developers discussion and problem solving Subject: [AccessD] Filtered combos - Events don't fire I ran into something that I don't remember, or perhaps I never quite figured out. In a subform, the Exit and LostFocus events of a control do not fire if you click entirely out of the subform into the parent form or into a control on another subform. That is a PITA! It appears that the logic is simply that the control never lost the focus IN IT'S FORM. Unfortunately this wreaks havoc with setting the unfiltered sql back into the combo's RowSource property. What a PITA. John W. Colby www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com