A table name does not prove the records are inside this file
An Access front end can list linked tables whose rows live in another database, spreadsheet or server. This tool does not follow links or connect to those sources. The linked-table section is an inventory of references, not an export of their records.
Open the original database in its authorized environment to identify each link and export that source separately. Do not move credentials or connection strings into a public report. This package deliberately does not expose connection passwords or fetch external locations.
Plan separate handling for rich fields
Attachments and multivalue columns are complex structures, not ordinary text cells. OLE fields can wrap documents or application-specific binary data. This release lists these fields but skips their values, and binary columns have the same explicit boundary.
Record how many attachment-bearing records and multivalue selections exist in the source. Extract files and a stable parent-record key using an appropriate Access workflow. Retain a mapping between each extracted file and its source row before deleting or retiring the original database.
Use relationships as a map, then rebuild constraints
A recorded child field and referenced parent field help explain how tables fit together. Composite relationships produce multiple column records; preserve their ordinal order. Linked endpoints require the corresponding external data before joins can be checked.
Excel and CSV do not enforce Access referential integrity. Indexes, default expressions, validation rules, calculated expressions, saved queries and VBA are not recreated. Rebuild required behavior in the destination, then compare joined record counts and orphan records before switching applications.