I see powerapps was recommended. It's Microsoft's most recent answer to the corporate perception that Access proliferation is problematic. I tend to disagree that it's problematic when all things are considered - Primarily the fact that the cost benefit to rapid development outweighs the perceived risk in many cases. Powerapps has a bunch of momentum but it's not full Access parity.
We move Access Apps all the time when it makes sense and not when it doesn't. A good first start is to move the backend to SQL Server and keep the front end in Access. SQL Server Migration Assistant for Access makes the data migration a cinch. Some changes will be needed to the Frontend after a bunch of testing to fix the minor differences after which point the migration is transparent to users.
Then consider replacing parts of the front end in a modular fashion - one user story at a time. Maybe this bit can be replaced by PowerApps and these other bits by a more robust WebApp.
Take a look at Radzen for rapid development of webapps over data (generates C# Server and either Angular or C# Blazor App)
We move Access Apps all the time when it makes sense and not when it doesn't. A good first start is to move the backend to SQL Server and keep the front end in Access. SQL Server Migration Assistant for Access makes the data migration a cinch. Some changes will be needed to the Frontend after a bunch of testing to fix the minor differences after which point the migration is transparent to users.
Then consider replacing parts of the front end in a modular fashion - one user story at a time. Maybe this bit can be replaced by PowerApps and these other bits by a more robust WebApp.
Take a look at Radzen for rapid development of webapps over data (generates C# Server and either Angular or C# Blazor App)