Macro is throwing runtime error 13 after 4 years of operation

%3CLINGO-SUB%20id%3D%22lingo-sub-1556864%22%20slang%3D%22en-US%22%3EMacro%20is%20throwing%20runtime%20error%2013%20after%204%20years%20of%20operation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1556864%22%20slang%3D%22en-US%22%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20running%20office%202016%20pro%20plus.%20I%20have%20an%20excel%20macro%20that%20started%20throwing%20the%20runtime%20error%2013%20code%20today.%20This%20macro%20is%20in%20three%20separate%20sheets%20connected%20to%203%20separate%20data%20sources%20running%20in%20a%20solid%20automation%20setup%20with%20years%20of%20service.%20The%20incoming%20data%20has%20not%20changed%2C%20nor%20have%20the%20sheets%20been%20modified.%20Is%20there%20an%20issue%20with%20an%20update%20maybe%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1556864%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMacros%20and%20VBA%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Greetings,

 

I am running office 2016 pro plus. I have an excel macro that started throwing the runtime error 13 code today. This macro is in three separate sheets connected to 3 separate data sources running in a solid automation setup with years of service. The incoming data has not changed, nor have the sheets been modified. Is there an issue with an update maybe?

0 Replies