After researching the web for the error # I've come to understand that the problem to which I refer is a MS bug and requires a lot more time and effort to clear than I'm willing to invest--I'll live with the minor OL inconvenience.

This thread is finished as far as I'm concerned.

Mark