logo
search
File Cannot Open

Fix Access Workgroup Information File Errors in C# Application

Muhammad TalhaMuhammad Talha Sep 28, 2026 869 views

Question details

The user needs to resolve an OLE DB connection error in a C# application indicating that an Access workgroup information file is missing or opened exclusively.

How to Fix Access Workgroup Information File Errors in a C# Application
Product
Microsoft Access / C#
Device & OS
not provided
Scenario
Connecting to a password-protected or secured Access database from a C# application using an OLE DB connection string.
Observed behavior
The C# application throws an exception stating the workgroup information file is missing or opened exclusively by another user when attempting to connect to the database.
Before you start

Ensure no other users, background processes, or open instances of Microsoft Access are locking the database or MDW file in exclusive mode before testing your C# connection string.

Solution 1Recommended

Update Connection String for Password-Protected Database

Use this solution if your database is encrypted with a password but does not use an MDW file for user-level security.

Many connection errors occur when developers mistakenly include workgroup parameters for a database that only requires a standard password. Adjusting the connection string to match the encryption type is the most direct fix.

1
Verify encryption method

Determine if the Access database is simply password-protected rather than secured with user-level security (MDW). Open Microsoft Access, click 'File', then 'Info' to check the encryption status.

2
Modify the connection string

In your C# code or App.config file, remove any 'SystemDB' parameters from your OLE DB connection string, as they are not needed for basic password encryption.

3
Add the database password

Append 'Jet OLEDB:Database Password=YourPassword;' to your connection string. For example: 'Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\path\database.accdb;Jet OLEDB:Database Password=MySecret;'.

Update Connection String for Password-Protected Database
Connection Provider: Make sure you are using 'Microsoft.ACE.OLEDB.12.0' (or later) for newer .accdb files, whereas 'Microsoft.Jet.OLEDB.4.0' is generally used for older .mdb files.
Free Microsoft Office alternative

Experience a Free and Lightweight Office Alternative

While WPS Office does not handle Access databases or OLE DB connections, it provides an exceptional, free alternative for your everyday document, spreadsheet, and presentation tasks. It offers full compatibility with Microsoft Word, Excel, and PowerPoint formats in an easy-to-use interface, making migration effortless.

  1. 1. Download the installer: Visit the official WPS Office website and click the Free Download button to get the latest version.
  2. 2. Install the suite: Run the downloaded executable file and follow the on-screen instructions to install the software on your device.
  3. 3. Open your files: Launch WPS Office and directly open your existing DOCX, XLSX, and PPTX files to continue working seamlessly.
Fully compatible with Microsoft Office formats like DOCX, XLSX, and PPTX.Lightweight software with significantly faster startup times.Familiar, tabbed user interface for seamless and intuitive migration.All-in-one suite encompassing Writer, Spreadsheet, Presentation, and PDF tools.
QA img-9

Frequently Asked Questions

What is an MDW file in Microsoft Access?

An MDW file is a Workgroup Information File used by older versions of Microsoft Access to store user-level security data, including user accounts, passwords, and granular permissions for database objects.

Why do I get an 'opened exclusively by another user' error?

This error occurs when a user, an application, or a lingering background process has opened the database or the MDW file in exclusive mode. This prevents any other external C# application from establishing an OLE DB connection.

How do I connect to an Access database without an MDW file?

If the database only uses standard password encryption without user-level security, omit the SystemDB parameter entirely. Simply include the 'Jet OLEDB:Database Password=[your_password]' parameter in your C# connection string.