SharePoint vs Access as Front-end Application
Posted on 2011-05-06
We are trying to make a decision on what front-end application environment to use between MS SharePoint or MS Access. In both cases, the work will be done by an outsider vendor. Here is the background info:
We have developed a version of what we needed 6-7 years ago in MS Access. This application was design to use Access as a front-end and a back-end on two separate databases. However, unfortunately, we did not implement the application due to internal issues not related to the program. Most of the logic in the program still sound however, there are many other needs and changes happend in the company that would need to be included. Some of the business rules and processes changed over the years. In addition, since then, we also added another division. Their needs are more complex and process driven. We recently virtulized most of our server systems and invested in a new standalone SharePoint 2010 server. It has SQL 2008 back-end and waiting for the development. We have also decided that SQL to be the back-end for Access if implemented.
I would like to know the following:
1. Can you list a very high level list of disadvantages/advantages of using SharePoint as a front-end application to work with SQL 2008 over MS Access?
2. Can the Access code (VBA) be transferred over to SharePoint environment?
3. If we reused the existing Access code and build on it, and not use ShaprePoint in our application development, what are the disadvantages/advantages of doing so?
Thank you for your help.