Access/VBA reporting case study
Review an anonymized migration involving more than 1,900 generated historical reports.
Prove that the new system still produces the results the business trusts.
A migration is not complete because the new screens look right. Soligent builds evidence around the reports, calculations, data transformations, and rules that must remain dependable.
Request a Legacy System AssessmentWhen visual review is not enough
Small differences in rounding, grouping, date handling, labels, filters, or historical data can change a report while remaining difficult to spot manually.
- Totals differ only for certain periods or customers
- Exported spreadsheets shift labels or values
- New queries treat nulls and dates differently
- Stakeholders cannot explain which output is authoritative
Build a trustworthy baseline
Verification starts by identifying representative cases, known edge conditions, reliable historical data, and the exact outputs that are safe to compare.
- Representative and boundary-case datasets
- Known-good report samples
- Calculation and formatting rules
- Documented exclusions for unverifiable source history
Compare behavior systematically
Depending on the system, evidence can include automated regression tests, data reconciliation, cell-by-cell report comparison, and reviewable discrepancy reports.
- Values, formulas, labels, and ordering
- Rounding, aggregation, and date logic
- Filters, permissions, and workflow outcomes
- Traceable disposition of every material difference
Approve only what the evidence supports
Soligent separates explained differences from defects and refuses to convert unreliable history into a misleading pass result.
- Investigate material discrepancies
- Correct code or baseline assumptions
- Record residual risks and exceptions
- Tie acceptance to reproducible evidence
Take the next step with clarity.
Start with the system, the operational risk, and the evidence needed to make a sound decision.
Request a Legacy System Assessment