I've used a component of Add-In Express to get around this issue. It's only $150.
I had to deal with this same issue trying to send Outlook email from Access. I used Outlook Redemption, a third-party COM library that wraps the calls to Outlook and avoids those annoying popups. It is free unless you want to redistribute it, in that case you would need to buy the redistributable version for $199.
How Outlook Redemption works
Redemption is a regular COM library; once registered on the system, it is accessible to any programming language (VB, VBA, VC++, Delphi, etc). Redemption uses Extended MAPI (which is not affected by the Security Patch since it is not accessible to the scripting languages) to duplicate the functionality blocked by the Security Patch. All Safe*Item Redemption objects have an Item property which must be set to an Outlook item. Once set, you can access any properties and methods, both blocked and not blocked. For the blocked properties and functions, Redemption objects completely bypass the Outlook object model and behave exactly like Outlook objects with no Security Patch applied. For the properties and methods not blocked by the Security Patch, all calls are transparently forwarded to the Outlook object that you assign to the Item property. With this approach changes to your code are minimal: you only change the way you declare the objects, but not the rest of your code that actually accesses both blocked and not blocked properties and methods.