|laziness, impatience, and hubris|
Translating the Access db (tables, queries, forms, reports, etc.) into Perl/MySQL/HTML would be a mammoth task, risky, but I think doable. I'm well aware of the view that tinkering with old, creaking legacy dbs is dangerous (been there, done that).
If tinkering with old, creaky legacy is dangerous, then why upgrade at all? "Office 2010 is being launched," you write, but by whom? Why at your office?
If you must upgrade, could it be three years in the future, giving you time to develop your own solution?
Is it possible to test the Microsoft upgrade path for feasibility, just as you might pilot a migration away from an MS-centric approach?
Just documenting all that your system does, and that a new system would be required to do, might help planning how you might pursue either approach.
In reply to Re: OT: Moving a legacy MS Access db to a nix/MySQL server