A Vision for Modernizing Microsoft Access - A Proposal

A Vision for Modernizing Microsoft Access

Dear Microsoft Access Team,

As a longtime user and admirer of Microsoft Access, I’d like to share some ideas for modernizing and future-proofing this remarkable tool. Access has been a cornerstone for database-driven applications, but I believe it has the potential to reach new heights with the following updates:

1. Upgrade Forms to HTML5 + CSS
   Replace the current forms system with HTML5 and CSS, allowing for responsive and adaptive designs. This change would enable Access applications to function seamlessly across desktops, tablets, and mobile devices, enhancing versatility and usability.
2. Support for JavaScript as a “Code-Behind” Language

In addition to VBA, introduce JavaScript as an alternative for coding. JavaScript’s modern ecosystem and developer familiarity would attract more users and open up new development possibilities.

3. Modernize Reports with HTML5 + CSS

Update the reporting system to output results in HTML5 and CSS. This would provide greater flexibility for customized designs and make reports compatible with web and mobile interfaces.

4. Reintroduce Application Splitting and Deployment

Reinstate and enhance the ability to split databases into a back-end and a front-end application. Allow developers to export front-end applications created in HTML5, CSS, and JavaScript for hosting on web servers like IIS or deploying to the cloud.

5. Cross-Platform Portability

By adopting technologies like HTML5, CSS, and JavaScript, Access could be made portable across platforms, including macOS. This would address a long-standing demand from Mac users while opening up new markets. Making Access cross-platform would further solidify its position as THE premier database development tool.

6. Standalone Application Compilation

Introduce a feature allowing Access to “compile” applications into standalone executables or deployable packages using a web server wrapper. This would allow apps to run without Access being installed, eliminating the need for an “Access Runtime Edition” and simplifying deployment.

7. Launch (again) an “Access Developer’s Edition”

Create a dedicated Access Developer’s Edition, sold separately from Office, with advanced tools tailored for developers. This edition would serve as a powerful but accessible alternative to Visual Studio, focused on creating portable, platform-independent database applications.

8. Flexible Integration with Office

While keeping Access standalone, provide optional integration with other Office apps through exposed libraries. This would give developers more control over how they interact with Word, Excel, and Outlook, or not at all if the goal is to be fully portable.

These updates would not only modernize Access but also position it as the go-to tool for lightweight, platform-agnostic database development. With cross-platform potential and standalone application capabilities, Access could meet the growing demand for versatile, efficient, and independent database solutions.

Thank you for your time and for considering these suggestions. I’d love to hear your thoughts and discuss how we, as a community, can help shape the future of Microsoft Access...

Or is this the recipe FOR THE REPLACEMENT of Microsoft Access? ;-)

Sincerely,
Fabrizio

An Access Developer since version 1.0