If I understand the problem, I think the CurrentProject.Path property would work since your associated folders are relative to the folder that contains the db. Therefore, it should not matter what the drive letter is - just populate a variable and append the subfolder paths to it as needed. You can make the variable project-wide in scope or call it from any module when needed. If you are faced with UNC paths some of the time and sometimes not, you'll have to use string functions to repace the \\CompanyServer (fake name) with a drive letter.
Actually, to deal with this on a corporate basis, I removed the drive letter and replaced it with the UNC path reference because not everyone had the same native drive letter on the network.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.