![]() I'm not sure what's going on with 2016 vs 365 but I've been reading around and all the factors I can find, pertain to either the operating system or the project references. I took the same exact macro file and opened it on a PC that had Office 365 and the macro ran perfectly. I commented out erasing the arrays and tried again, and it gave me another mismatch error on the first if statement of my code. They used the macro to import a file and encountered a Mismatch error, and the error line made no sense to me because it was just erasing a loaded array. Yesterday someone tried using the macro on a different PC (Still Windows 10), but had Excel 2016. ![]() This entire time the macro has been created, edited, and used with office 365. I made a macro that others have been using the last 6 months with 0 unexpected errors until yesterday.
0 Comments
Leave a Reply. |