Hi John, a friend asked me this very question over the weekend, and while I didn't have access 2007, I did have access 2003. so, I opened it up and began to try some very basic things.
I was amazed and unhappy to see how badly window eyes worked with access. I checked the manual, no chapter on working with access. the latest set file was for access 2002 (xp), so I had no idea if that was of any help; however, if it was, then god help those before that set file! it could be that ther are portions of access 2003 which work well with window eyes and I just didn't find them, but the ones I found hardly worked at all, except for using the mouse cursor. every control was the same type, making reclassing to improve things impossible, and there were no scripts of course. It's also possible 2007 has improved it's accessibility, so you won't run into the problems that I did. On a separate note, window eyes does not read any of the intellisense dialogs for any office product in the 2003 family, and I suspect in the 2007 version as well. I have a script which does this for me, and assuming you'll be doing vba programming, you'll also need, so I'll start working on packaging it up so you can test it. I do test on a module name which may be specific to the 2003 release of office, in that case these scripts won't work for you until I can get that module name for 2007 and adjust the scripts. I'll be getting 2007 installed in a few weeks, but if you want to hurry things long, could you go into the VBA ide and get the module name for me when in there? What I'm asking for is for you to go into the code editor window, and use a script like the virtual explorer to see what the module name and original class of that window is? in 2003 the module name is VBE6 and the original class is VBAWindow. I need to know if these are the same for 2007. to go into the code editor, you could go into ms word, press alt-f11 to go into the VBA development environment, and press f7 to go into the code window. I have a lot of e-books on access 2007 I could email you; you'll need to send me a request to my home address at: [email protected] and remind me what you need. Chip ------------------------------ Chip Orange Database Administrator Florida Public Service Commission [email protected] (850) 413-6314 (Any opinions expressed are solely those of the author and do not necessarily reflect those of the Florida Public Service Commission.) > -----Original Message----- > From: John W. Carty [mailto:[email protected]] > Sent: Monday, May 04, 2009 9:57 AM > To: [email protected] > Subject: access 2007 > > Is anyone working with access 2007 and WE 7.01? I'm a long time > mainframe programmer and I've just been given a project to design an > access 2007 database application and I've never used access. > > I'm most interested to learn how to best navigate access with > WE and how > to configure access for best use with speech. > > Any information that could get me started would be great. > > John Carty > > If you reply to this message it will be delivered to the original > sender only. If your reply would benefit others on the list and > your message is related to GW Micro, then please consider sending > your message to [email protected] so the entire list will > receive it. > > All GW-Info messages are archived at > http://www.gwmicro.com/gwinfo, and can be searched through > and sorted using the search > form at the bottom of the page. > > If you wish to unsubscribe from this list, send a message to > [email protected] and include leave gw-info in the body > of the message. > > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.
