Microsoft Excel file with macros doesn't work when on the drive

Sorry I am having the same problem as original poster. I had an Excel spreadsheet that has macros that I cannot get to work in the shared drive. I don't know what changed because they used to work but now I can only get it to work if I save it outside of Dropbox or if I remove Dropbox for Teams from Excel. However, if I remove Dropbox for Teams, the auto sync for all files stops working. I did what was suggested here and tried updating the registry to both 1 and 2 but nothing allows me to have the macros run with in the Dropbox shared drive anymore.

Here is the screenshot. I made Dropbox a trusted site, but still can't get rid of this error unless I remove Dropbox from Teams which then eliminates auto sync for all the files.

Thanks for the additional info and the screenshot, lanos.

Can you try the following steps (if you haven't already) and let me know if they help?

1. Ensure your Dropbox file is fully synced and stored locally on your computer.
2. Open File Explorer.
3. Locate your Excel file, right-click it, and select Properties.
   • If you see an Unblock button or checkbox, click it and then Apply.
4. Open Excel.
5. Click File.
6. Click Options.
7. Click Trust Center Settings.
8. In the Trust Center window, select Trusted Locations
9. Click Add new location.
10. Click Browse to locate your local Dropbox folder and select it. Ensure the Subfolders of this location are also trusted box is checked.
11. Click Ok to add it.
12. In the Trust Center window, go to Macro Settings.
13. Select an option that enables macros such as Enable VBA macros.
14. Click Ok.
15. Restart Excel and open your file from your trusted Dropbox folder.

Hannah​ thanks for these steps. With Dropbox for Teams, the option to Unblock in Properties is no longer available. I verified all the other options had been selected as you detailed, but macros still do not work and I get the same error message.

Hi lanos, thanks for the info regarding this matter. In order to look into this behavior in more detail, I'd recommend contacting the support team directly for them to investigate further.