Short answer is no, not automatically. When you import tables into Access, the table structure and data come over, but relationships do not. Relationships live at the database level, not inside the table itself, so Access treats them as separate metadata and leaves them behind. That is why when you import tables one at a time, you always end up having to recreate the relationships manually.

There are a few ways to make this less painful. If you import all related tables in one operation using External Data -> Access, Access will usually recreate the relationships for you as long as the table and field names match exactly.

Another approach is to use a staging ACCDB that already has all the tables and relationships defined. You update that database, verify everything looks good, then replace the old one or relink to it. You can also export the entire database to a new ACCDB and then delete what you do not need. It is clunky, but relationships are preserved because they were never lost in the first place.

If this is something you do repeatedly, the most robust solution is to recreate the relationships with DAO in VBA so it is a one-click operation instead of busywork. This is more complicated, but makes for the best solution.

One important side note is the "1" that Access appends to imported tables. That only happens because the table already exists. If you delete the old table first and then import, the name will stay the same and any automated relationship logic becomes much simpler.

Also, and this is worth saying, re-examine why you need global system relationships in the first place. Personally, I rarely use them unless I have a very specific reason. Cascade updates are never necessary because I always use autonumbers. Cascade deletes are dangerous, and I do not like letting the engine silently delete related data behind my back. I handle most of that logic explicitly in code so I know exactly what is happening and when.

In many databases, relationships are more about documentation than enforcement. If you can handle validation, updates, and deletes cleanly in code, you may not need to rebuild relationships every time at all.

Hope this helps.