That's what I thought too and I found another thread with the same
information so I suspect you're right. :-)
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Co-author of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/boo...x#AboutTheBook
Word FAQ:
http://mvps.org/word
TechTrax eZine:
http://mousetrax.com/techtrax/
MVP FAQ site:
http://mvps.org/
"Bob Buckland ?:-)" 75214.226(At Beautiful Downtown)compuserve.com wrote
in message ...
Hi Beth,
As a guess, from the other times I've seen a similar case of this
reported, the registry change that fixed it in those cases was to
locate registry key
HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing
Tools\1.0\Override\en-US
and check the list of DLL and LEX entries to see if they're pointing to
real or nonexistant files.
If non existant (probably a pair)
Rename these to oldDLL and oldLEX (although I suspect that exporting then
zapping that key then running a diagnostic would also
work).
But, just a guess 
=============
"Beth Melton" wrote in message
...
Thanks so much for passing along the resolution - what you encountered is
indeed odd!
btw, did they happen to give you a support number? If so, would you mind
emailing it to me (I wouldn't post it in the newsgroup). I can ask someone
from Microsoft to look it up and supply the exact steps they used to
correct
the issue. It would be nice to have for future reference.
--
Bob Buckland ?:-)
MS Office System Products MVP
*Courtesy is not expensive and can pay big dividends*