Rich:

We need to know more about what you're doing to ascertain what's
causing the problem. Are you running a simple macro? Is the macro (or VBA
code) firing off immediately when the workbook opens? Is the workbook
accessible by others? Give us more hints.

Steve in Ohio

"Rich in Yorktown" wrote:

Started getting this error message today. Seems as if I turned something one
unknowingly. It now gives this message on code that has been running for
months.

Any ideas on a remedy would be greatly appreciated.
Rich
Win 2000/office 2000