Finally! Thanks for the that useful tip rondelv! This does appear to be the
cause of the problem and explains why it works in our Exchange 2003 test
environment and not on some others out in the field.
According to the KB details (http://support.microsoft.com/kb/911829/),
Microsoft introduced a new editor based on an iframe rather than the good
old activeX control used previously. I'm guessing that the new iframe must
be using some new tricks since ieSpell does support many popular iframe
based editors like TinyMCE.
I'll get my testers to set up a new Exchange env with the patch to check out
the problem. Thanks for the lead and sorry for the wait!
Cheers
Sidney
From: iespell%40yahoogroups.com">iespell
yahoogroups.com [mailto: iespell%40yahoogroups.com">iespell
yahoogroups.com] On Behalf Of
rondelv
Sent: Tuesday, 16 October, 2007 10:38 PM
To: iespell%40yahoogroups.com">iespell
yahoogroups.com
Subject: [iespell] Re: Outlook Web Access
For what it's worth, I too, after using iespell for a long time, am now
having problems with it not checking spelling.
Specifically this happens in OWA with Exchange 2000. And, even more
specifically, a patch has been installed Exchange 2000 (see KB911829)
that changes the behavior of the editing controls. This fix is also
available for Exchange 2003.
I cannot say for sure but I believe the problem with iespell started
after the hotfix on Exchange was installed.
At the moment, for me, iespell works fine when spell checking in non-
OWA instances such as Yahoo Mail. However, iespell does not check the
message text body of the when using OWA but it does check the spelling
in the To:, From:, CC:, etc. fields.
Any help would be appreciated.
[Non-text portions of this message have been removed]
.