Over the past couple of decades I have developed an Access "project" (ADP) front-end to a SQL-Server database for a client.
They are still running SQL Server 2008 R2, and the Access front-end is still being developed under Access 2007, after Microsoft dropped support for "projects" in more recent Access versions.
At my client's site, the SQL Server database runs on their own server, and each user has an "ADE" copy of the Access front-end on their own PCs, that connect with the SQL Server database.
My client would now like to move to a web-hosted system, allowing their own staff and customers to access their data from pretty much anywhere.
Do we have to start from scratch? This client has been running their business since the late 1970s, and they now have quite a sophisticated application that has grown from a pre-MSDOS platform, through MS-DOS, and into its current Access / SQL-Server incarnation. It would be good if we could somehow make use of the existing SQL Server database and Access work. I'm pretty sure SQL-Server databases can be hosted on the cloud (I connect to my client's database remotely using its IP Address), but is there a suitable web-based front-end that would be compatible with my Access application?
Can anyone point me in the direction of a migration path that might achieve this? If not, to any case studies of anyone else who has achieved this sort of conversion? I can't be the first person faced with this task!
Any suggestions or help gratefully received.
Azure is one platform that can host SQL Server databases, and if your application is built to true client-server specs, then you can do this. If not, then you'll have a good bit of work to do to make it so. Here's a migration writeup that may help: https://datamigration.microsoft.com/scenario/access-to-azuresqldb?step=1. Again, I'm not sure if this is even relevant with the ADP format.
One of the best ways to handle this is to use a Remote Desktop Service (RDS) setup. If you use RDS, users can remote in from anywhere and work just like they were sitting at their desk in the office. It can be pricey to setup and maintain, but it would require virtually no changes in your Access db. You can do this entirely with Microsoft products, or you can use Citrix, or other 3rd party products like Thinify (https://www.cybelesoft.com/blog/convert-access-web-app/?cn-reloaded=1).