Charlotte Foust
cfoust at infostatsystems.com
Fri Mar 17 11:25:47 CST 2006
Well, it IS Friday, so we can all go nuts together! LOL Charlotte -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin - Beach Access Software Sent: Friday, March 17, 2006 9:14 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] KeyDown Problem Once again, I find that I am not losing my mind. (Or have company anyway) Rocky Charlotte Foust wrote: > I have, and it drove me crazy! When strange things start occurring, I > immediately do a compile. The thing that's making me nuts now is, > after installing Office 2003 but keeping Access 2002, this has become > even more frequent. Error messages will pop up that occur deep down > in the stack but they present an obtuse message that is less than > useless and I have to step through layers of code to find the line that blows up. > > > Charlotte Foust > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky > Smolin > - Beach Access Software > Sent: Friday, March 17, 2006 6:16 AM > To: Stuart McLachlan; Access Developers discussion and problem solving > Subject: Re: [AccessD] KeyDown Problem > > Stuart: > > Thanks. That would be the global solution. > > Had another weird problem occur - one of my events stopped working > altogether. It was a click event. Other events continued to work, > this one just wouldn't. Eventually I traced it down to a compile > error in an unrelated module - it was in another form's code! Once I > had a clean compile, the click event worked. Any compile error and > this event stopped. Although other events continued to work correctly. > > Ever seen this behavior before? > > Regards, > > Rocky > > > Stuart McLachlan wrote: > >> On 16 Mar 2006 at 5:58, Rocky Smolin - Beach Access Software wrote: >> >> >> >>> Stuart: >>> >>> Thanks for having a look at this. (You might have to relink the >>> back >>> > > >>> end tables.) >>> >>> Login as Curly - password curly. >>> >>> The tabbed form and KeyDown routine are in the Orders form off the >>> Main Menu. The tabbed form IS full of sub-forms. Someone suggested >>> that might be causing problems. >>> >>> >>> >> Yes, that's it. Once you tab to another page, the subform gets the >> focus and that subform doesn't have KeyPreview on. You will need to >> set keypreview on for all the subforms. Then call a generic procedure >> > in the keydown to shift focus back to where you want it. > >> >> >> > > -- > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com