Microsoft Access modernization
Moving an Access application to the web is not a one-click conversion. The practical path is to preserve the data and business requirements, then rebuild the user interface, permissions, reports, and automation for browser-based use.
PHPRunner generates the new web application from the database structure. Existing Access forms, reports, macros, and VBA remain useful as specifications, but they are not automatically converted into browser pages or application code.
Quick answer: Inventory the current Access application, move the data to a server database when required, connect PHPRunner, generate the first web application, and then recreate the Access-specific interface and logic with PHPRunner pages, events, and permissions.
The database provides the starting structure for the new application.
After PHPRunner connects to the database, it can generate browser-based list, add, edit, view, and search pages. You can then add reports, dashboards, authentication, role-based permissions, validation, and application events.
If the Access database contains well-structured tables, primary keys, and relationships, much of the data-entry foundation can be generated quickly. The amount of additional work depends on how much behavior currently lives in Access forms, queries, macros, reports, and VBA.
An Access interface is a desktop design, not a web-page definition.
| Access component | Web migration approach |
|---|---|
| Tables and relationships | Keep them in Access for a Windows-hosted application, or migrate them to a server database such as SQL Server, MySQL, or PostgreSQL. |
| Queries | Review each query and recreate the required SQL, database view, or application data source for the target database. |
| Forms and subforms | Use them as workflow references, then design new browser pages and master-detail relationships. |
| Reports | Rebuild required reports with PHPRunner report, chart, dashboard, or printable-page tools. |
| Macros and VBA | Identify the business rule behind each routine and implement it with PHPRunner events, PHP, JavaScript, SQL, or database logic. |
The right choice depends on hosting, traffic, and long-term maintenance.
PHPRunner can connect directly to a Microsoft Access database, but the deployment requires a Windows web server, the Microsoft Access Database Engine, appropriate folder permissions, and the PHP COM extension. The Microsoft Access connection documentation lists the current requirements.
For a small internal application, a direct connection may be sufficient. For more users, concurrent updates, remote hosting, or future growth, migrate the data to a server database before building the final application. Test data types, primary keys, indexes, relationships, and queries after migration.
Separate the data move from the interface rebuild.
The old screens show what users need, while the new pages are designed for the browser.
The following example begins with an Access order form. Its fields, related records, calculations, and actions provide the requirements for the replacement page.
The required workflow is then rebuilt in PHPRunner’s Page Designer. This is a new browser-page design, not an automatic conversion of the Access form.
PHPRunner generates the finished web page from that project configuration.
No. PHPRunner generates web pages from the database, but Access forms and their layouts must be recreated for the browser.
Yes, when the documented Windows server, database-engine, permissions, and PHP requirements are met. Many projects move the data to a server database for scalability and hosting flexibility.
They do not run in the generated web application. Recreate the required business rules with application events, PHP, JavaScript, SQL, or database-side logic.
No. Access-specific SQL and functions may need to be rewritten for the target database. Test every query used by forms, reports, exports, and automation.
Often yes, but both interfaces must use a carefully planned data source and update process. Avoid uncontrolled copies of the same data, and define which system is authoritative during each migration stage.
A phased migration is easier to verify than a simultaneous rewrite of every screen.
Choose one useful workflow, such as order entry, equipment tracking, or case management. Rebuild it from login through reporting, test it with the people who use the Access application, and apply what you learn to the remaining modules.
The Access-to-web PHPRunner page provides a concise product overview and trial form. This Solution Center guide explains the migration decisions and limitations in more detail.