Max Wanadoo
max.wanadoo at gmail.com
Fri Mar 6 07:21:24 CST 2009
> this is a little over the head of my target audience in the Classes and Events lecture series. Ha! You can say that again... Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: 06 March 2009 13:14 To: Access Developers discussion and problem solving Subject: Re: [AccessD] Filtered combos - Events don't fire Yep, this is where I am headed. This is the reason that I keep the clsFrm public in a form header, it allows other objects to reach into the form, grab a pointer to the clsFrm and tell it to do things (like reset the combo queries). Unfortunately this is a little over the head of my target audience in the Classes and Events lecture series. John W. Colby www.ColbyConsulting.com Gustav Brock wrote: > Hi John > > Use the OnEnter and OnExit events of the subform control of the main form to track this. > > /gustav > > >>>> jwcolby at colbyconsulting.com 05-03-2009 21:52 >>> > 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