John Colby
jwcolby at ColbyConsulting.com
Fri Mar 17 11:21:46 CST 2006
Ahhh, but Office 2006 is coming any day now, and that will fix ALL of our problems. BTW, I have an opportunity only for list members. Send me $10,000 and I will invest it and return you 1 MILLION dollars in a month, GUARANTEED. John W. Colby www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Friday, March 17, 2006 11:28 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] KeyDown Problem 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