Macro Enable only one time

[EricC35]

I have a program that I have been developing. I save a new version from time to time when I make substantial enough modifications. Some versions of the saved program start the macros bringing up the userform after enabling only the first time in a new version. Other saved versions require that macros be enabled each time. Why would this happen in some saved versions but not all versions? How can I cause my program to require that macros only be enabled once? I share this program with many others, so I would like for them to only have to enable it the one time.

 

[CSyx]

Are all iterations of the file saved in the same location? The only thing I can think of is that in the Options the Trust Center has the location saved. If the file is saved in a trusted location....I don't think you would get the enable macro's prompt at all.

 

[EricC35]

Good suggestion. Both files are saved in the same location. When I made changes an older one, I would save as a new version in the same location. For some reason, version 2.1 start the user form every time after it was first enabled, but version 2.2 needs to have it enabled every time. There was nothing changed to the security settings from one to the other. I checked the Trust Center locations for both files side-by-side on separate screens and they were identical. Your suggestion of making the their location a "Trusted Location" worked in now that my problem is solved because they both open to the user form without having to enable first. Now when I go to save a new version such as 2.3, it doesn't ask even the first time if I should enable macros. Is this a good idea to have my "Documents" folder as a trusted location? Wouldn't that mean that anything I download would be able to start running macros immediately? Sounds kind of risky!

 

[CSyx]

It could be risky. Any file in that folder will run a macro upon opening the file. If you set up a specific folder as a trusted location I wouldn't put ANYTHING in that folder unless I have previously confirmed it is a safe file. If these are files you are creating ( I never tried this before) you could possible look into the Trusted Publishers settings. Then set yourself up as a trusted publisher. Then it wouldn't matter where the file is saved. And you wouldn't run the added risk of having a whole folder set as a trusted location.