jwcolby
jwcolby at colbyconsulting.com
Mon Sep 24 12:05:17 CDT 2007
Yep, it wasn't you I was addressing, that would be like preaching to the choir. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Monday, September 24, 2007 12:45 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Current control I know, John. My controls are ordinarily bound to a control class that handles this. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Monday, September 24, 2007 9:21 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Current control And this is exactly where a framework comes in so handy. As a form loads, it loads classes for controls. These classes can set a pointer to a framework ctlCurrent when the control's OnEnter fires, and set a pointer to the framework ctlPrev in the control's OnExit event. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Monday, September 24, 2007 11:41 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Current control Trouble is, when is either PreviousControl or ActiveControl the right one. Clicking on buttons, option buttons, tab control tabs, etc., mess up the logic. I generally have created a property for the form CurrentControl and set it in the enter event (or whatever's appropriate). Since I don't set it for buttons or tab controls, etc., it's more reliable than the built in methods. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Sunday, September 23, 2007 6:55 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Current control On 23 Sep 2007 at 12:16, Arthur Fuller wrote: > In my experience, Susan and Shamil, I have found it useful to identify > the previously active control -- because clicking on a button or other > control repositions the ActiveControl. For example, if I have a button > the user can click, and she does so, then I have lost track of the > control she was previously on. I use a static function for this purpose. > What's wrong with just using Me.PreviousControl ? -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com