That's a nice theory, Garry. Can you explain then why a system that was installed originally with Windows 7 and Office 2010, and has code originally developed on it in Excel 2010, would suddenly start spitting out this error? Steve's solution is the only one I found that resolved it.