Jun 01, 2010
Although Microsoft Access can be used to create desktop applications, its Web development features are lacking. If an organization wants to port an existing Access application to the Web, typically its done in one of two ways:
* The organization can create a brand new Web-based application in Visual Studio. The server-side code would then use the .NET framework to read and write to and from the Access database. Note, however, that the Access software itself is not even being used in such a scenario. This scenario is very time consuming and requires trained developers with web development and AJAX skills.
* The organization can install Access Services on a SharePoint server, and then use the Web-development tools that exist in Access.
For Access developers, the latter is the most natural approach, as the organization can continue developing within Access. However, the introduction of SharePoint into the equation substantially increases the costs and introduces some other complications.
In this white paper, we consider the costs of both possibilities, and then we provide an alternative.