IMPORT/EXPORT DATABASE ... TYPE ACCESS

[rhamenator]

Parent: #137
Related: #138

Track Microsoft Access database-container interchange beyond current VFP parity work.

Scope ideas:

• IMPORT DATABASE ... TYPE ACCESS
• EXPORT DATABASE ... TYPE ACCESS
• schema/table/relation/container mapping for Access MDB/ACCDB assets
• import/export of saved queries and other container metadata where feasible
• compatibility boundary between data-only interchange and fuller application migration

Notes:

• This is real, committed scope. Reclassified 2026-09-01: this is now an active v1 blocking criterion, not sequenced after current parity-closure slices -- part of the migration pipeline (Database/container interchange and migration bridges #137) that v1 does not ship without.
• Pick this up as an explicit selected Access modernization target per the roadmap's sequencing rule (docs/05).
• Expect phased implementation because Access data containers and application surfaces are tightly coupled.

Children (scoped 2026-09-04):

• I-migration/#141 slice: Access container format notes (clean-room, read-only reconnaissance) #5474 Access container format notes (clean-room, read-only reconnaissance)
• I-migration/#141 slice: EXPORT DATABASE ... TYPE ACCESS #5475 EXPORT DATABASE ... TYPE ACCESS (phase 1: SQL-script output, blocked on I-migration/#141 slice: Access container format notes (clean-room, read-only reconnaissance) #5474)
• I-migration/#141 slice: read-only Access container schema inspection #5476 read-only Access container schema inspection (blocked on I-migration/#141 slice: Access container format notes (clean-room, read-only reconnaissance) #5474)