[AccessD] Filtered combos - Events don't fire

Charlotte Foust cfoust at infostatsystems.com
Thu Mar 5 15:02:17 CST 2009


I always had to have a secondary routine in the GotFocus and Enter event
of the parent to handle that situation.  It's because of the order of
precedence of the events.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Thursday, March 05, 2009 12:52 PM
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




More information about the AccessD mailing list