Scrapped Gauges in an Access Migration: Migrate or Archive?
Leaving retired instruments in the old .accdb looks tidy, until a complaint reaches a gauge you scrapped two years ago. How to scope them.
Leaving retired instruments in the old .accdb looks tidy, until a complaint reaches a gauge you scrapped two years ago. How to scope them.
A dropped gauge isn't due for calibration, but it can't measure again. The as-found reading, possession trail and record ISO 9001 7.1.5.2 c expects.
A PASS tells an auditor nothing about drift or impact. How to carry point-level as-found/as-left data out of MET/TEAM 3.3.x, and prove it arrived intact.
A MET/TEAM 3.3 upgrade and a migration both need ISO/IEC 17025 7.11 validation. Compare the two packages side by side before budget close.
Two technicians, one Access calibration record, one dialog box. How 'Save Record' can erase an as-found result without a trace, and how to close the gap.
One delete on a retired gauge can take years of calibration records with it. Check your Access relationships before your next audit or migration.
Your Access calibration history says 'JS' did 1,400 calibrations. Before you migrate, prove who that was, or an auditor will ask you instead.
Your Access Pass column can't say 'adjusted', 'limited' or 'not assessed'. How to reclassify legacy calibration results before migrating.
He left in June. His micrometer is due in November and still in his name. How to offboard calibrated gauges before an auditor finds the gap.
A one-time seat plus 20% maintenance looks cheap on the quote. Here is the 3-year line-by-line math your controller will ask for: seats, servers, upgrades.