Dan and Suzanne, I'm sorry you're taking this attitude, but flaming a person with a legitimate problem isn't a solution. The solution you proposed (the link) simply isn't the answer in this case, and any solution shouldn't require special knowledge or a
person with a degree in computer science to implement. As the original complainant said, this problem just cropped up recently, and it could easily be a software bug in a "fix" to another problem. Lord knows, this software is complex enough. I will agree
with those who say Microsoft's support system is flawed. Most companies will handle legitimate support requests without imposing outrageous charges, but it seems Micsosoft's attitude is a bit of "Let 'em eat cake." Anyway, the solution I proposed works for
me, a bit annoying but effective, but I'm not saying it would work for anyone else.
P.S. I was a mainframe systems programmer working on mostly big IBM mainframes for about 40 years and mostly in assembly languange. While I don't have that level of expertise on PCs, I have been working with Word ever since it came out in the mid-80s including
writing complex macros (Why, oh why, do they keep screwing around with the macro language?) and before that (beginning in 1981) I had a Xerox Star terminal on my desk, the forerunner of all things Windows and Word.