You're welcome for what little help I was able to provide.
I agree that using a button is better. It's not like a user
can't cancel the spell check ([pssin;y by mistake) and then
have to edit the comment in some innocuous way to rerun the
spell check. To avoid that kind of stupid editing, you
really should have the button anyway/ But if you have the
button, why bother with the AfterUpdate event.
I am still thinking about why you got the error message and
I guess my memory is faulty. I think I may have known my
memory was not reliable once or twice before but forgot
about it ;-)
In any case, I dug up a couple of my old apps and reviewed
where I had used spell check before.
and behold, I had
also used a button, probably for the above reasons.
On further contemplation, I can see a possible scenario of
how spell check might work. It's at least conceivable that
spell check uses the comments text box's Text property to
update the corrections. Since setting the Text property
(unlike the Value property) does trigger the usual chain of
events (including Before and After Update). There's bound
to be trouble because the initial AfterUpdate has not yet
completed.
--
Marsh
MVP [MS Access]
Marsh I put the code into a command button and it works fine so that will
do, in fact its properly better there.
Thanks very much for your help.
"Marshall Barton" wrote