Fellow MVP Alum George Hepworth just recently flagged a new ‘feature’ that he ran into in which at the startup of his database he suddenly started receiving a message box stating
Yes | NoMicrosoft Access
What We Know About This New ‘Notification’
It would seem this is a new ‘feature’ that was introduced in Version 2304 although there is no mention of it in the Release Notes (3 Resolved issues, but no Feature updates listed):

We are told that the message box gets triggered the first time you try to make a connection via a macro or code if it is done at the opening of your database (and this will happen every time you open your database from my understanding).
So this isn’t a bug. This is Microsoft’s desired user experience!
More Information On The Issue At Hand
We are now starting to see threads surface in forums on the subject:
Moreover, several MVPs have expressed concern to the Dev Team about this sudden change.
My Take
Once again, I don’t understand the logic behind this unrequested change?! A feature no one asked for! Once again I question the priorities being work on, but what’s new there! I’m also floored that this made its way out of the concept phase, little alone internal testing. How did this even seem like a good idea and get released into Beta?
It is VERY common to perform such connections at the startup of a database by utilizing an AutoExec macro and VBA code, or by using a startup form with VBA code, so now with this ‘feature’ in place, users will constantly get harassed with the pop-up, cause unnecessary panic when they receive that message initially and will ultimately lead to users simply ignoring it and blindly clicking “Yes” to pop-ups. If this is supposed to be a new security measure, it is a major flop as far as I’m concerned.
Have Your Say, Provide Your Feedback
For what it is worth (you all know my thoughts on Microsoft actually listening to anyone!!!!!), this is your opportunity to provide feedback on this new ‘feature’! Don’t be silent and post your concerns to the Feedback Portal
and/or by using the Feedback command from within Access itself.
Oh well, moving on.
