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.
Dear Richard_1931,
About this issue, if you have sent the feedback to our related team, I suggest you keep eyes on the emails for the latest updates.
Best Regards,
Cliff
Jim, Thanks again for your continued efforts. I just got around to the macro problem again and tried to get an earlier version of Word from the Time Machine, but discovered that, for some mysterious reason, despite being set for automatic backup, my Time machine hadn't been backing up since March, and as I purchased the version of Word on my iMac in May, I didn't have an earlier version of it.
So I replaced my version of word with an updated one from the link you provided, https://docs.microsoft.com/en-us/officeupdates/update-history-office-for-mac. However, when I tried to create a macro, I again got that error message I was getting when I wrote to you about the problem: "Microsoft Visual Basic. System Error &."
I then checked the Applications folder in finder and it showed the Word app as being installed today and didn't show an earlier version. So it's looking like stalemate on macros. Do you have anything else to suggest?
**** Greene
If you have Time Machine running you can restore a previous build of just Microsoft Word.app
Before doing that, go to Word > Help (or any Office app Help) and choose Check for Updates to launch AutoUpdate. Set AutoUpdate to manual so it doesn't try to bring you back up to date as soon as you restore an old build.
If you don't have a Time Machine backup, you can download individual installers from this page:
https://docs.microsoft.com/en-us/officeupdates/update-history-office-for-mac
Once again, Jim, I appreciate your patience and sticking with me on this, but I've just encountered a new problem. After reading your latest message, I checked the two macros I created yesterday. They were still working, and I tried to create a third one for further verification, but in the process I did something wrong, I'm not sure what, and when I try to use any of the macros, I now get an error message reading
Microsoft Visual Basic
System Error
I tried to access Visual Basic Editor under the Macros Tool and wasn't able to. The rainbow wheel just kept spinning, because of the system error, I suppose. I then went into the list of macros in the Macro Tool and tried to delete the macro I was working on when the error message first appeared, but when I clicked on delete I got the error message. I then ran Disk Repair hoping that might fix the problem. It ran quickly and successfully, but that didn't fix the problem. Perhaps uninstalling Word and reinstalling it would solve the problem, but I don't want to do that if there's a simpler and more direct way of doing it. Can you offer any guidance?
Hi
I re-ran my tests. Whether or not the target document was open, the code runs to completion without error.
I don't remember whether or not I already offered this suggestion, but perhaps your file system needs a tune-up. It certainly can't hurt to check your volumes.