Shortcut Error with Access and Mapped Drives

[Guest]

If a shortcut is created pointing to a Microsoft Access file on a mapped
drive, it will run succesfully but throw up an error message "Windows cannot
find <path>. Make sure you typed the name correctly, and then try again."

The file runs without error if you navigate to the file on the mapped drive.
Only a shortcut to the file generates the error. We tried switching to a
UNC path instead of the mapped drive but the results are the same.

The same problem occurs no matter what computer within the network you try
to run it from.

 

[Guest]

The error appears to occur for other Access databases as well, so it does not
appear specific to the database.

A new thing I learned however that when run as a scheduled task it does not
throw up the error. Can someone explain this mysterious wall that exists
between priveleges a user has when running an application (even an
administrator) and the computer running an application?