// blog
Turning an Access Database into a Web App: What Changes for Your Team
When a Microsoft Access database becomes a web app, its forms become web screens in the same order, its VBA and macros are written down as rules and built once on the server, its tables and queries move to PostgreSQL or SQL Server with their results checked against Access, and its reports become print pages and PDFs. Everyone works through a browser with their own sign-in instead of sharing one file on a drive.

A lot of small businesses run on a Microsoft Access database someone built years ago. It sits on a shared drive, it slows down when a few people use it, and someone runs Compact and Repair when it misbehaves. Here’s what changes when it becomes a web app.
One database, not one file
Today everyone opens the same file. In a web app everyone works against one database through the browser, each with their own sign-in, user rights and a record of who changed what. Working from home stops being a special case.
Forms and reports
Forms and subforms become web screens with the same fields in the same order. Reports, with their grouping, totals and labels, become print pages and PDFs that look the same. Lists can still download to Excel.
VBA and macros
The logic in VBA modules, form events and macros is where the work is. Each rule is written as a plain sentence, checked by the people who use the database, and built once on the server.
Tables and queries
Tables move to PostgreSQL, or to SQL Server if you already have it. Saved queries are rebuilt, and their results are compared with Access before you switch. Linked tables and Excel imports become imports that check the data first.
How we know it works
The method is the one we used on two real desktop programs, Virtual Salesman and TurboCASH: rules written down, data moved, totals matched. See how an Access database becomes a web app. The first call is free.
































































































































