Key takeaways from this article

• What’s wrong with MS Access?
  There’s nothing inherently wrong when it’s used as intended. The real issue is that simple Access apps can quietly balloon into complex, mission-critical systems that Access wasn’t built to support.
• When should you not use Access?
  MS Access falters in multi-user environments, in projects that require integration, apps that require mobile access, or once your database grows past its 2 GB limit.
• Can we just build web apps directly over our Access database?
  Not reliably. Access has no native web deployment and its file-based engine isn’t designed for web concurrency. While you can connect a web server to an Access file for very light scenarios, it’s fragile and doesn’t scale. For web apps, you need to move the data to a server database (e.g., SQL Server, PostgreSQL, MySQL).
• How can you migrate Access to the web?
  As demonstrated in the below video, moving Access data to a relational database and building web applications over it is pretty straightforward with the right tools.

…

MS Access Modernization: Why (and How) to Move to the WebRead More »