Anyone that has ever created hyperlinks within a database, or stored file paths and then tried using the Application.FollowHyperlink method to open them has no doubt come across a security warning, such as:
Whether there is genuine cause for concern, such a message is quite alarming for end-users and can cause them to do all sorts of things (including calling IT stating they have a virus – true story).
So what can we do as developers?
Using VBA Code
Well, firstly, stop using hyperlinks. They are evil.
Now that we are storing things properly as plain text, we have full control over how we open files, so we don’t have to use the FollowHyperlink method which triggers such messages!
One excellent solution, 15+ years old, would be to use Allen Browne’s GoHyperlink function, refer to:

A second approach would be to use ShellExecute or another API driven solution. I explored some of this, so please refer to:
So the moral of this story is, stop using Hyperlinks and FollowHyperlink(), they only cause problems! They may be convenient, but they are simply not worth all the headaches that come along with them.
Did Someone Say Registry Hack?
If you don’t want to change your ways, there is another approach that can be employed via applying a registry hack. Refer to the following article from Microsoft to get all the details.

