An existing application in Microsoft Access can contain valuable accumulated expertise. Grassroot IT first establishes the tasks it performs and the results needed. Required improvements and technical choices follow from that understanding.
Understand data and business rules
Microsoft describes tables, unique keys and relationships as foundations of database design. Its database design documentation explains these connections. For the application, examine which data belongs together and which rules govern changes.
Test forms and queries using business examples, including duplicates, missing information and changes to linked data. Examine effects on other forms, reports and Visual Basic for Applications modules.
Derive architecture and operations from actual use
For multiple users, examine storage, concurrent access and distribution of the application version. Microsoft describes splitting the application and data files as one option. Its suitability depends on the real environment, not simply the number of files.
Justify replacement or a different database system through needs and constraints. For a continuing solution, organise ownership, approved versions and tested recovery. This supports understandable, gradual improvement of an existing application.