Microsoft Access to SQL Conversions
Converting Microsoft Access applications to true client/server n-tier applications is in our DNA. In fact, after having spent a couple of years developing and maintaining a commercial MS Access developer application that was used to programmatically modify the object model of Access applications, which was used by a large customer base of Professional Access Development freelancers and programming shops, we’re pretty confident in our expertise in the Access object model and how to equate everything in an Access application to it’s Visual Studio and SQL Server counterparts. At some point, every company that uses Access for mission critical applications will bump up against one or more of the following issues that will cause them to seek out the services of a professional software company to convert their Access program to a more reliable and stable platform: database size limitation, database corruption, backup issues, too many users, data collisions due to multiple simultaneous page edits, and remote user requirements.
AppDataWorks, LLC has been involved in many MS Access conversions. Our business started and evolved from projects of this type. There are a lot of reasons why it is not a good idea in the long term to build applications around Microsoft Access, and why it is more desirable to build true client/server applications around managed, compiled applications and secure SQL Server systems that are not easily exposed to the end user.
Converting MS Access Applications and Databases to true Client Server applications
Fault tolerance is the ability of a data system to recover from catastrophic failure. There is NO FAULT TOLERANCE built into Access MDB’s. We highly recommend Microsoft Access to SQL Conversions for any business using Microsoft Access for critical data. Mission-Critical data is data that your business relies on to operate on a day-to-day basis. You may find out too late that your MDB was not successfully backed up. Can you afford to have that happen?
SQL Server has the ability to recover data to a POINT IN TIME. It also has the ability to back itself up on any interval you choose even while the data and applications that use them are in use. Microsoft Access to SQL Conversions are performed to eliminate the limitations of Microsoft Access in this regard.
Even if you have your front end application in an Access ADP connected to SQL Server on the back end, you should still consider the benefits of a Microsoft Access to SQL Conversion. Access ADP application files can only be opened by one user at a time, requiring that each individual user has a copy of the most current application file. This requires a significant time investment in deployment of new versions. .NET applications can be deployed to a single network share or Web Server location for instantly updating all clients with very little deployment overhead.