Hi Folks,
I posted previously about my companies policy to ban all macros/VBA
Anyway the current solution was to issue a certificate to myself so I can sign the VBA code and the database should work as normal.
The database was stored on a file share and each user took a copy and ran it locally on their own machine. When I issued a new release of the DB they would grab that and work away
This worked briefly, I would sign the VBA and when a user started up the database they clicked on the "enable content button" and everything worked.
Now instead of the enable content options they get a warning saying that active content was disabled and to click here for details.
The message shows the certificate details and says that it has been tampered with and can't be trusted.
Any ideas why access gices this error when a file is moved or copied, I think this it all started when a windows 10 update was installed in mid to late February
TIA
I posted previously about my companies policy to ban all macros/VBA
Anyway the current solution was to issue a certificate to myself so I can sign the VBA code and the database should work as normal.
The database was stored on a file share and each user took a copy and ran it locally on their own machine. When I issued a new release of the DB they would grab that and work away
This worked briefly, I would sign the VBA and when a user started up the database they clicked on the "enable content button" and everything worked.
Now instead of the enable content options they get a warning saying that active content was disabled and to click here for details.
The message shows the certificate details and says that it has been tampered with and can't be trusted.
Any ideas why access gices this error when a file is moved or copied, I think this it all started when a windows 10 update was installed in mid to late February
TIA