Well, All I can say is that I'm back at work on an xp pc, and the same thing occurred.
This is office 2003 you're working with right? 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: Michael D. Lawler [mailto:[email protected]] > Sent: Monday, February 23, 2009 4:24 PM > To: [email protected] > Subject: Re: some info for MS Office developers > > I didn't have to do the first steps of associating the set or > detecting the cursor in XP. We'll mark this down to check > under Vista. > > > > At 11:45 AM 2/23/2009, you wrote: > >Hi all, > > > >our shop does a lot of work with "smart documents", which > have a lot of VBA > >code inside the document template to turn a document into an > application > >(usually we do this in MS Word docs). > > > >For anyone else working in the IDE of Word (at least Word > 2003) I wanted to > >mention that apparently window eyes ships with some settings missing. > > > >There is no set file associated with the IDE portion of > Word. you'll need > >to load the set file Word11, and save it with the > association to the IDE. > >it will save under the name VBE6, which I recommend you > keep, to allow you > >to change it distinctly from the document word set file. > > > >In addition, the cursor type isn't set in window eyes for the IDE, so > >arrowing up/down through the code will not speak. You need > to open a code > >window in the IDE, and then use the command to auto-detect > the cursor type > >(I believe that's control shift insert C by default), and > windows will > >properly determine what cursor type the IDE is using, and it > will then begin > >tracking the cursor properly. I was told that you didn't > need to save > >anything after window eyes determined the cursor type, window eyes > >automatically saved that info. > > > >Finally, you need to go into the tools | options menu of the > IDE, and in the > >"docking" tab, uncheck all the checkboxes for each window > type so that none > >of them are dockable (I did this so long ago I can't > remember which problem > >it solves). > > > >the only unsolved problem after this is that intellisense > doesn't speak, but > >maybe I'll be able to script that. > > > >I just wanted to put this info out there for others; it may > help with other > >versions of office, I don't know. > > > >hth, > > > >Chip > > -- > Michael D. Lawler > Voice 260-489-3671 > Fax 260-489-2608 > Internet mailto:[email protected] > web http://www.gwmicro.com > ftp ftp://ftp.gwmicro.com > GW Micro, Inc., > Development Liaison and Technical Support Supervisor > > 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.
