I need some expert opinions on the future of an Access Program I have
Posted on 2014-01-20
I have an Access program that is used by about 10 people. The company I created it for is merging with another and now there will be about 200 people who need to use it. Here is what I want to do, what I need to know:
1. Is it feasible?
2. Would this be a good way to go?
3. How hard would it be to do if it is the way to go?
4. Would speed be an issue?
Here is the setup:
The Access Program resides on a company server in the building. The Access Program has links to another program also on the server.
What I want to do:
1. I would like to split the Access Program and put the tables that are currently in the Access Program up on Azure. My understanding is that while Access is not very good with large groups, that Azure SQL would be able to handle 200 people hitting the data at the same time.
2. Each user would have their own front end put on their computer (the user would not be able to get into design mode because I would be using Access Runtime).
Now there are some people in the company that would like to see the whole Access Program scrapped and have it completely rebuilt so that it is a web based program. My concern with that is that the web based program would still need to be able to get to the data in that other program housed on the company server. Also we have shown this Access Program to web developers (3 groups as of now) and with each one their first question was "Why would you want to change this? It looks great and is doing exactly what you need it to". This leads me to believe that we can keep an Access front end and just put he back end on Azure (with links to that other program on the company servers.
What do the experts think? Am I stubbornly sticking to an old technology that people do not use anymore or can Access, with Azure, still be viable for a larger group?
Any opinions (and any links to websites for more info) are greatly appreciated and if you need more information (or if I have said anything "stupid" please excuse me, I am not an Access Expert, in fact I probably know enough programming in VBA just to be dangerous)