Your network access has been interrupted - MS Access application on Remote Desktop Web Access

It can be several reasons, please check on below:

1. Check Network Stability

• Ensure that the network connection between the RDWA server and the SQL backend is stable.
• Test for any intermittent network drops or latency issues that might cause the connection to break.

2. Adjust Remote Desktop Session Settings

• Configure the RDWA session to prevent timeouts:
• Open the Group Policy Editor on the RDWA server.
• Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits.
• Set the "Set time limit for active but idle Remote Desktop Services sessions" to Never.

3. Split the Database

• If not already done, split the Access database into a front-end (local to the user) and a back-end (on the server). This reduces the risk of corruption and improves performance.
• Ensure the front-end is stored locally on the RDWA server and not on a network share.

4. Use Persistent Connections

• Access assumes a constant connection to the backend. If the connection drops, even briefly, it can cause errors.
• Consider using a persistent connection to keep the database linked:
• Open a hidden form when the application starts.
• Use VBA to maintain a connection to the backend:

Dim db As DAO.Database
Set db = CurrentDb

5. Test with Local Tables

• Since even local tables are throwing errors, this suggests the issue might be related to how Access interacts with the RDWA environment.
• Test the application on a local machine (outside RDWA) to confirm whether the issue persists.

6. Update MS Access and Drivers

• Ensure that MS Access is updated to the latest version.
• Update the ODBC drivers used to connect to the SQL backend.