Mark A Matte
markamatte at hotmail.com
Thu Mar 16 12:55:25 CST 2006
About 2 years ago I had an experience where I instantly developed the "mouseophobia" disease. I developed an app for around 20 users. On the 3rd day of 5...I was directed to the last machine to load said app. When I got there I was introduced to the user...and the JAWS system. The last user was visually impaired and could not use the mouse. For the next 48 hours I re-engineered all of the functionality to not need a mouse. It was definitely an educational experience, and is always just under the surface as I take on new projects. Mark A. Matte >From: "Penn White" <ecritt1 at alltel.net> >Reply-To: Access Developers discussion and problem >solving<accessd at databaseadvisors.com> >To: "Access Developers discussion and problem >solving"<accessd at databaseadvisors.com> >Subject: Re: [AccessD] Key Preview Problem >Date: Thu, 16 Mar 2006 11:48:04 -0500 > >I share your mouseophobia and my users didn't request it either. I'm not >even sure they'll even use the Alt keys and have wondered several times why >I was doing this but I do it anyway. > >Because of the subforms, I don't think Lambert's suggestion will work >though. I think I'd still have to put code in each subform that gets the >focus but I'll give it a try just to be complete. > >BTW, I was wrong about putting the KeyDown code in the Form_KeyDown event >handler. It works fine. I'd forgotten that I had more than one subform on >the tabbed page and was coding the wrong subform...oh well. > >In any event, I've had a great time exploring this with everyone and have >learned a lot. Thanks to all. > >Penn > >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com