Allow us to trust our own networks IP address
In our company's view of security, it will not allow network mapping by server name.
When creating a multi user system, mapping by drive letter adds several user or system complications. Getting all users to have identical mappings is virtually uncontrollable, and trying to locate the back ends by guessing what drive it's on, needs very advanced programming.
But it is currently IMPOSSIBLE to trust any network if mapped by IP address. Even the generally recognised 'home' ones (192.168, or 10.1)
Not even by modifying the registry.
Users get irritated by constantly having to enable the code, and in some cases it's too late by then to run it properly.
We finally got round that by turning off ALL VBA warnings. Hardly ideal, but MS seems to think that that is preferable.
So come MS: It's OUR data, on our network.
Surely there's a way to let us trust it by IP address.?