We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


MS Access program on shared drive doesn't open correctly from a particular CPU

Medium Priority
Last Modified: 2013-11-29
                 I use an Access program which is located on a shared drive (Z).  I recently acquired a new CPU, and mapped to the Z drive and connected to this program.  When I run the Access program on my computer I now get an initial error which says that the program cant find an image on the C drive. This image is the background image for the initial user Form and is stored on the Z drive. Access cant find any of the 12 different Form images and somehow is looking for them on the C drive.
      The program feeds a separate database also stored on the Z drive. I have tried a shortcut, copying and directly accessing the Access program but all result in the C drive error.  My mapping is correct and matches other users who have no errors. I can logon to other computers and the program works.  My content is enabled. Please help.
Watch Question

try using the UNC path instead of a mapped drive path.  Here is a tip from www.aadconsulting.com  for an easy way to obtain the UNC path.

In Access, select a table and right-click. From the popup menu, click Create Shortcut...
In the Create Shortcut dialog, check the This Database is on the Network
checkbox, and you can then copy the full UNC network path from the Full Network textbox.


                    I think you may be on to something. But let me clarify. I can go to the folder where the front end resides and use it correctly from one workstation. When I go to my workstation and go to the same folder and use the same front end it does not work correctly. My original concern was that a link between the front and back was broken but the problem is dependent on where Im sitting?
      Should I try to use a UNC to link my pc to the front end or to link my front end to the back end or something else?
the back end.  This link should answer all your questions regarding setting Access up to run on a network.  Read it in its entirety.

One last thing about linking the FE to the BE is that you need to always use what is called UNC path names (Universal Naming Convention). All this really means is that you REALLY REALLY REALLY do not want to use mapped drive letters when you link. Besides, mapped letters are a 20 year throwback to the old PC DOS and CPM days when we used floppy disks! (When is the last time you used a floppy disk). Don't use mapped drives to a file share on the server. Drive mappings have all kinds of problems. Just plugging in a USB jump drive (memory stick) into your computer and the drive mappings can change. Further, you have to setup EACH pc for drive mappings and that is a pain. Further, even plugging in a digital camera can change drive letters. So, just avoid drive letters and mapping like the plague. Simply put, don't use them, and they are horrible from a support point of view. If you do risk using drive letters, then you will get a large increase in support calls for your software.

In other words, always use a path name to the back end files. What this means is when you use the linked table manger, always navigate through network places to the server, and then to the folder, and then the back end mdb file. DO NOT use mapped drives, and do NOT use the linked table manager to navigate to a back end by a drive letter.  

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.