I lost a lot of respect for Microsoft when I first saw that issue. It’s such an easy to avoid limitation. Like probably a similar level of difficulty to remove that limitation than to write the error message explaining it, unless it’s more of a spaghetti mess than I’m expecting it to be.
If you want to reference other files, you should use a less ambiguous way to refer to them. Like a relative path or full absolute path. The fact that that weakness is because of a half-baked feature like that actually makes me lose even more respect.
Edit: thanks for the info though, it does add some missing context.
I lost a lot of respect for Microsoft when I first saw that issue. It’s such an easy to avoid limitation. Like probably a similar level of difficulty to remove that limitation than to write the error message explaining it, unless it’s more of a spaghetti mess than I’m expecting it to be.
It’s to do with the ability to work with data across all open workbooks:
You can reference
[Workbook.xlsx]Sheet1!B2but if you have two excel workbooks open, both namedWorkbook.xlsxwhich one should be used?If you want to reference other files, you should use a less ambiguous way to refer to them. Like a relative path or full absolute path. The fact that that weakness is because of a half-baked feature like that actually makes me lose even more respect.
Edit: thanks for the info though, it does add some missing context.
So throw an error at runtime on that macro, most workbooks aren’t the target of a macro
Whichever one has the smallest relative path to the workbook using it? How does it find the workbook if it isn’t open already?
It doesn’t.