Deploy a Microsoft Access Application with SQL Server and Remote Desktop
Question details
The user needs a secure way to give field users access to an existing Access and SQL Server application while planning for future browser access.

- Product
- Microsoft Access, SQL Server, and Remote Desktop Services
- Device & OS
- not provided
- Scenario
- Internal staff need access to current data, reports, and calculations, with a possible web interface for external users later.
- Observed behavior
- The desired setup keeps a shared relational database while supporting remote use of the existing Access front end and gradual web development.
Identify the Access front end, its SQL Server connection, and the users who need remote or browser access. Check Remote Desktop Services and Access licensing, server capacity, and your organization's security requirements before deployment.
Publish the Access Front End Through Remote Desktop Services
Use Remote Desktop Services or RemoteApp to give internal users remote access without rewriting the existing application.
Install Access or a suitable Access Runtime on the Remote Desktop Session Host, and verify that the application opens and connects to SQL Server.
Deploy a separate copy of the Access front-end file to each user's profile or session environment, and keep the shared data in SQL Server.
In Server Manager, configure a Remote Desktop Services deployment and publish the Access application as a RemoteApp, or provide an authorized remote desktop session.
Use an approved access path such as Remote Desktop Gateway or a VPN, enforce multifactor authentication where supported, and grant SQL Server users only the permissions they need.
Sign in as a typical user through the RemoteApp feed or remote desktop connection, then test data entry, reports, calculations, and simultaneous use.

Add an ASP.NET Web Interface to the Shared SQL Server Database
Use a gradual web migration when external users need browser access or the application requires extensive custom logic.
Use WPS Office for Documents and Spreadsheets Alongside Your Access Application
WPS Office is a free, lightweight Office alternative with a familiar interface for documents, spreadsheets, and presentations. Its Microsoft Office format compatibility helps teams move everyday files between suites, but it does not replace Access, SQL Server, or Remote Desktop Services.

Frequently Asked Questions
Can users run the existing Access application remotely without rewriting it?
Yes. Install the required Access software on a Remote Desktop Session Host and publish the front end through RemoteApp or an authorized remote desktop session. Users then connect to the server rather than running the application locally.
Should each remote user have a separate Access front-end file?
Yes. Give each user a separate front-end copy in their profile or session environment while keeping shared tables in SQL Server. This helps avoid conflicts caused by multiple users opening the same front-end file.
Can Access and an ASP.NET application use the same data?
Yes. Both can connect to the same SQL Server database while the web application is developed. Apply appropriate permissions and test that both interfaces handle shared data and business rules consistently.
Should I replace SQL Server with SharePoint Lists?
SharePoint Lists can work for smaller, simpler tables, but SQL Server is generally the better fit when the application depends on extensive joins, queries, calculations, and relational data.
Can WPS Office replace the Access application?
No. WPS Office can help users work with documents and spreadsheet reports, but it does not replace an Access application, its SQL Server backend, or its Remote Desktop deployment.




