'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Microsoft Access Requires Workgroup Rejoin on VPN Disconnect
Question details
Microsoft Access denies permission to open a database when the VPN is disconnected because the secured .MDW workgroup file on a network drive cannot be reached, requiring a manual workgroup rejoin.
- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Opening a secured Access database linked to an .MDW file stored on a network drive while the VPN connection drops or is unavailable.
- Observed behavior
- Access denies permission to the database and requires users to rejoin the workgroup once the network connection is re-established.
Verify that your VPN connection is stable and that you have the necessary network credentials to access the shared drive hosting the .MDW file before launching your database.
Ensure VPN Connection Before Launching Access
Prevent the workgroup file disconnection by ensuring the network drive is reachable prior to opening the database.
Because Microsoft Access heavily relies on continuous file access over the network, opening a secured database without an active connection to the .MDW file will result in an immediate permission denial.
Open your VPN client and establish a secure connection to your corporate network.
Open Windows File Explorer and navigate to the shared network drive where the .MDW file is stored to ensure it is accessible.
Once the drive is accessible, launch Microsoft Access and open the secured database as usual.
Rejoin the Workgroup Manually After Disconnection
If the VPN disconnects while Access is open, you will need to manually point Access back to the .MDW file once the network is restored.
Migrate Away from MDW-Based User-Level Security
User-level security (.MDW) was deprecated in Access 2007. Modernizing your database security prevents these legacy network issues.
Looking for a modern, lightweight Office suite?
While WPS Office does not include a database management tool like MS Access, it is an excellent, free alternative for all your Word, Excel, and PowerPoint needs. Experience a lightweight, modern interface with high compatibility for standard Office formats, ensuring seamless document management without legacy network headaches.
- 1. Download the installer: Visit the official WPS Office website and click the free download button.
- 2. Install the software: Run the downloaded executable and follow the on-screen prompts to complete the setup.
- 3. Open your files: Launch WPS Office and easily open your existing .docx, .xlsx, or .pptx files.
Frequently Asked Questions
Why does Microsoft Access use an .MDW file?
The .MDW (Workgroup Information) file is used by older versions of Microsoft Access (.MDB format) to store user-level security settings, passwords, and permissions for various database objects.
Can I use .MDW security on modern .ACCDB databases?
No, user-level security using .MDW files was officially deprecated starting in Access 2007 and is no longer supported in the modern .ACCDB database format.
How do I prevent the VPN from locking my Access database?
Ensure your VPN client is configured for persistent connections. For a more robust solution, consider migrating your Access backend to SQL Server, which handles intermittent network connections much better than file-based sharing.
