Your suggestion is a good one. Subsequently, I discovered that LASERFICHE
(LF) also causes this problem (Geekette's Blogette). Though the article
referenced a 2007 version of LF as well as WORD 2007. I have a support plan
w/LF for my version 8.1. I will call on Monday and will see what they know
before messing with the registry.
Thanks for your help. Not many would have gone to the kb article and then
made a suggestion. I appreciate that.
EM
"db" wrote:
> I was reading in the kb
> you provided that it does
> apply to version 12.
>
> so look for a similar key
> for version 11 however,
>
> you might want to make a
> system restore point and
> then follow the advice the
> kb article says.
>
> and if word doesn't work
> with the mouse, you can
> restore the system point
> to restore the registry.
>
> the system restore point
> can be executed in both
> normal mode and safe
> mode.
>
>
> --
>
> db·´¯`·...¸>
> DatabaseBen, Retired Professional
> - Systems Analyst
> - Database Developer
> - Accountancy
> - Veteran of the Armed Forces
> - Microsoft Partner
> - @hotmail.com
> ~~~~~~~~~~"share the nirvana" - dbZen
>
> >
> >
>
> "Edward Monet" wrote in message news:770F4B90-14FD-4420-B15D-425C9D038B75@microsoft.com...
> > I ran SAFE MODE. The mouse still does not work in WORD 2003. Any other ideas?
> > EM
> >
> > "db" wrote:
> >
> >> you might try to boot
> >> into safe mode and
> >> test both word and the
> >> mouse there.
> >>
> >>
> >> --
> >>
> >> db·´¯`·...¸>
> >> DatabaseBen, Retired Professional
> >> - Systems Analyst
> >> - Database Developer
> >> - Accountancy
> >> - Veteran of the Armed Forces
> >> - Microsoft Partner
> >> - @hotmail.com
> >> ~~~~~~~~~~"share the nirvana" - dbZen
> >>
> >> >
> >> >
> >>
> >> "Edward Monet" wrote in message
> >> news:C2748924-C554-44DD-9864-D3678E1BAA9D@microsoft.com...
> >> > The mouse works everywhere except in WORD 2003.
> >> >
> >> > FIX it MSKB 940791 applies to WORD 2007 with the same problem, but not WORD
> >> > 2003. Does a parallel registry fix apply to 2003, or is it an install issue?
> >> >
> >> > Thanks
> >>
288C181-52D0-40BC-8AE2-4E1A9A8AB23F@microsoft.com...