Welcome. I guess one way would be to develop your macro on the oldest version of excel it is supposed to run on. In this specific case, why not resolve the compile errors in 2013 and then see if its forward compatible to 2016? One point to consider is whether the errors are caused by missing or different dll add-ins. I have had issues with this in the past - you may just have missing dlls.