Excel files stored in dropbox that have a password protected VBA project, show a userform in the course of their use, and are closed before saving changes (choosing to save changes when prompted), cause a prompt for the excel VBAProject Password after excel closes.
This only occurs when Dropbox Badge is enabled and never occurred prior to Badge's implementation.
This problem is similar to that described in the Microsoft knowledge base (https://support.microsoft.com/en-us/kb/280454) but doesn't involve a COM add-in (removing COM addins or setting their connections to false has no effect).
It has exactly the same symptoms as the problem with the Acrobat PDFMaker Excel add-in several years ago (https://forums.adobe.com/message/5916268).
It would appear that Badge is interfering with proper closing of Excel and releasing of file references.
Here is a link to a simple file that replicates the problem when it is stored in a Dropbox folder on PC and Badge is active: https://www.dropbox.com/s/36s8ct1n2i5r5yg/Simple%20Password%20Prompt%20Generator.xlsm?dl=0
I can confirm this occurrence, additionally; it does not just affect documents stored in drop box, but any OPENED document with a password protected VBA project that utilizes UserForms.
If the document is opened, the userform is opened, then the document is closed and the application is closed (Excel) the password will appear regardless if its stored within Drop Box.
Hi Moss and Nate,
Thanks a million for reporting this! I just wanted to let you know that our product specialist is currently looking into this issue.
We'll update you as soon as we have narrowed down the problem. Please hang in there for us for now!
Just a quick update. We have been able to reproduce this behaviour and have alerted our engineering team. They are working on identifying a fix. Unfortunately, there is no timeline for it yet. We'll definitely keep you posted!
Thanks for your patience!
Sofia thank you for the Update! I am looking forward to the resolution to this issue and appreciate all of your return feedback to let me know where it stands.
I'll second that! I'm glad to know that you're working on it, and I appreciate your quick response to begin addressing the issue. The Badge added a feature I had really been hoping for (knowing when someone else is working on a file), so I was disappointed when I found it was also causing this error. Hopefully the issue can be resolved I and my clients can begin taking full advantage of the Badge's capabilities.
Unfortunately we don't have a resolution yet. Our engineering team is still working on a fix.
Thanks again for your patience.