Do Not Install Microsoft Access Add-ins and Databases in the Program Files Folder

Featured

Follow

Technical Support

• July 03, 2013 16:52

Installation Folder Background

Years ago, our setup programs defaulted to install itself in the C:\Program Files folder since that was Microsoft's recommended location for installing software. However, our more recent setup programs intentionally prevent installation in that folder. This is because Microsoft has made directories in the Program Files folder READONLY ever since Windows Vista. To prevent viruses that attacked and modified program files like EXE files, Windows prevents files in that folder from changing. It doesn't matter if you have administrator permissions.

Problem for Microsoft Access Add-ins and Databases

This poses a problem for our Microsoft Access add-in products or any Access databases you install. Unlike an EXE file, Access add-ins are Access databases. Though we ship our add-ins as ACCDE or MDE files so that the code can't change, they still change to store new data and link to tables in other databases. When installed in the Program Files folder, these modifications are not allowed and unexpected errors may arise.

For example, this error may be triggered in Total Access Analyzer if the program is installed in a READONLY folder: Error 91: Object variable or With block variable not set

Solution

Our products now avoid this problem by not allowing installation in the Program Files folder and installs by default in on one of two places:

• If installing for yourself (user installation), it defaults to your private Users folder
• For Machine installation, it defaults to a folder on your C: drive, which you need to ensure you have READ/WRITE rights

If you are installing one of our older versions, be sure to override the default Program Files folder and select a folder where you have WRITE permissions after installation.

0

• 

  Permanently deleted user

  • August 17, 2017 13:26

  Question to FMS:  You say that your products now default to either the "private users folder" or "a folder on the C: drive" to resolve the read-only issue.  I have both a C: drive and a D: drive on my machine and my D: drive is 4 times larger than my C: drive - for a reason.  In most cases, where possible and when a program offers the option to specify where it gets installed (most do),  I do not install any applications directly to the C: drive so that the drive does not become congested and instead install applications to the D: drive which in my case is much larger.  This keeps the C: leaner and helps to keep drive response higher and caching to a minimum.  The "private users folder" is usually on the C: drive and using a folder on the C: drive is still... well, the C: Drive.  So, can your products use a drive/folder designation other than the C: ???   If not, may I suggest you provide that option during install?
  
  

  0

  Comment actions Permalink
• 

  Rachel Gomez

  • January 05, 2023 05:37

  Microsoft products now avoid this problem by not allowing installation in the Program Files folder and installs by default in on one of two places:

  If installing for yourself (user installation), it defaults to your private Users folder
  For Machine installation, it defaults to a folder on your C: drive, which you need to ensure you have READ/WRITE rights
  If you are installing one of our older versions, be sure to override the default Program Files folder and select a folder where you have WRITE permissions after installation.

  Regards,

  Rachel Gomez

  0

  Comment actions Permalink

Please sign in to leave a comment.