Open a Secured MDB Database with an MDW File in Access 2016
Question details
The user needs to open a legacy, secured MDB database in Access 2016 using its MDW workgroup file and restore a launch command that previously worked.
- Product
- Microsoft Access 2016
- Device & OS
- Windows 10; previously Windows XP
- Scenario
- An older Access application uses an MDB database, an MDW workgroup file, and a VBA Shell command to launch the application.
- Observed behavior
- The launch command fails, and Access reports that the database was created with another version. Using a newly created workgroup file displays a login dialog, but the original credentials do not work.
Identify the MDB's original Access format and locate the original MDW file, valid credentials, and the installed MSACCESS.EXE path. Arrange conversion testing on a separate copy of the daily-use database with an account that has the necessary administrative permissions.
Convert an unsupported legacy MDB to Access 2003-compatible format
Use this approach when Access 2016 cannot open the database because its underlying file format is too old.
The .mdb extension alone does not identify the database version. Access 2016 supports Access 2000 and Access 2002–2003 MDB formats, but older formats such as Access 97 require conversion with an earlier Access release.
A format conversion does not automatically replace the workgroup file or remove user-level security. Keep the original MDW and authorized credentials available throughout the process.
Open a test copy using the Access version that previously ran the application, or ask the application administrator to identify whether it is an Access 2.0, 97, 2000, or 2002–2003 database. Do not assume that every MDB needs conversion.
Launch a compatible earlier Access release with the original MDW specified through the /wrkgrp command-line option. Sign in using an authorized account with permission to open and convert the database.
In Access 2003, use Tools > Database Utilities > Convert Database > To Access 2002–2003 File Format when that conversion is available. Save the converted database under a separate name. Very old formats may require an intermediate conversion in another compatible Access release first.
Open the converted MDB in Access 2016 with the original MDW explicitly selected. Test sign-in, linked tables, forms, reports, and VBA before replacing the production application.

Launch Access 2016 with the original MDW workgroup file
Use this approach when the database format is supported but the launch command selects the wrong executable or workgroup file.
Plan an authorized migration from secured MDB to ACCDB
Use this option for long-term modernization when the application no longer needs legacy workgroup-based security.
Use WPS Office for documents and spreadsheets alongside your Access application
WPS Office is a free, lightweight, easy-to-use alternative for everyday Office documents, with a familiar interface and Microsoft Office format compatibility to simplify migration. It does not open secured MDB databases, use MDW authentication, or fix Access 2016 compatibility errors; keep a compatible database application for those tasks.

Frequently Asked Questions
Can Access 2016 open every MDB database?
No. MDB files can use different Access formats. Access 2016 supports Access 2000 and Access 2002–2003 MDB formats, while older databases require conversion using a compatible earlier Access release. In Access 2003, the conversion entry point is Tools > Database Utilities > Convert Database.
How do I tell Access which MDW file to use?
Specify it in the launch command with /wrkgrp, for example: "C:\Path\MSACCESS.EXE" "C:\Data\Application.mdb" /wrkgrp "C:\Security\Application.mdw". Replace the example paths with your actual files and use the original application workgroup file.
Why do my credentials fail with a newly created MDW?
The new MDW may contain different security identities, even if the usernames look the same. Launch Access with /wrkgrp pointing to the original MDW and use the original credentials. If that file is missing, contact the database administrator to locate it or follow an authorized recovery process.
Will a new Access front end solve the version error?
Not by itself. Access 2016 must support the back-end database format, and access to a secured MDB still requires valid workgroup authentication and permissions. Convert an unsupported back end first, then configure and test the front end's linked tables.
Can WPS Office replace Access for this secured database?
No. WPS Office does not provide an Access-compatible MDB database engine or MDW authentication. You can export permitted data from Access through External Data > Text File and open the resulting CSV in WPS Spreadsheets, but the database application must remain in a compatible database tool.




