Help with migration strategy RRS feed

  • Question

  • Hi,

    I was contracted by a company to create a quite complex Access database. It is, of course split into 2, front and back end. This was always only a stop-gap just so all the employees could get access to client information ASAP. So currently, each user's PC has a copy of the front end on it (it has to use temporary tables, for reasons I will not get into here) and the back end is on a server. So it currently can only be access from their office. It is a small firm with no dedicated IT staff, so they asked my opinion on a way forward. As they have Sharepoint and Office 365, I suggested a move to Azure, so they could keep their Sharepoint stuff, and I could convert the Access backend into an SQL Server backend and write a web app (using HTML, CSS, JS and C#) that could access the DB from both home and the office. I know how to code this the old-fahsioned way, i.e. using a traditional web hosting service with database capabilities, but not using a cloud service. So, what is the easiest/best solution architecture for them, and can I use my current skillset (Access, C# inc ASP.NET MVC, HTML, JS and CSS) to access their data with this architecture? Obviously, I want to be the one doing the work for them, so is there anything else I will need to learn?

    thanks, Chris

    Wednesday, July 3, 2019 7:29 PM