If you weren't getting the SQL message before, and now you are, that
suggests to me that an update has been applied recently and it probably will
affect behaviour in this way.

One approach to diagnosis is to go back through recent updates in Control
Panel|Add and remove software, try to determine the update that caused the
change in behaviour, and look up the associated articles on the Microsoft
site - although they don't always tell you everything that changed in the
update. The trouble is that even if you manage to determine which update (if
any) changed this, you still have to decide whether or not to remove it, and
so on. Since it's probably there for a good reason, that may be a difficult
decision.

Another approach is - if it is relatively easy - to change the code and see
if that makes the difference. If it does, you may not know /for sure/ what
the cause is, which is always a bit disconcerting, but at least your system
works again. I don't like fixing stuff because of changes made by a software
supplier any more than the next person does, but in the end I usually end up
biting the bullet and doing it.

There are other possible causes such as the document becoming corrupted,
changes to the associated template or normal.dot, and you could for example
do stuff like rename normal.dot, recreate your document, and so on to see if
document behaviour reveted.

Not much more I suggest!

Peter Jamieson

add the suggested code
If the code is relatively easy to add, I would add it and see if it fixes
the problem, then consider the options