This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When I create macros in the 2019 version of Word for Mac as a way of opening frequently used files, the macros work immediately after I create them, but then anywhere from a few minutes to a day later I get the following error message: "Sorry, we can't find your file. Was it moved renamed or deleted." I didn't have this problem with the previous version of Word for Mac or any of the earlier versions of Word I used from back to about the late 1980s, tho those were for Windows-based PCs.
Does anyone have any idea what's causing this problem and how to fix it?
FYI, I'm creating the macros the way I always did, clicking on Tools, then Macros, then Record Macro, then entering in the Keyboard Shortcut box the keys I want to use, then opening the file I want to create access to, then going back to Tools and clicking Macros and End Recording.
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi Richard,
Did you give any consideration to my suggestion that your code might not be handling windows as effectively as it could?
Though I've given attention to all your suggestions, I don't recall one about code. In fact, I don't even know what code refers to. The problem with macros only arose when I had to get a new Office Suite in October of last year for my new iMac, as my old Office Suite was no longer supported. So the problem seems to be in Office Suite for Mac not in anything in my computer.
If code refers to how I create macros, I create them exactly as I did when I had the earlier version of Office Suite.
It occurred to me that the behavior you're seeing can happen if a macro isn't working with the worksheet that it thinks it is working on.
For example, your macro code might say something like:
With Activesheet
do something
End with
When you wrote or recorded the Macro you were working on one worksheet. But later, for some reason that particular worksheet isn't the one that is currently the active worksheet.
A better way to do it when making your macro is to specify exactly on which worksheet you want the action to happen
With Sheets("Sheet2")
do something
End With