Dividing mdb to data part and control part

[dannis]

Hello,

I've got divided my "some.mdb" to data part and control part with Access
2003 master.
As a result Access created a new file named "some_be.mdb", it contains
tables only.
Also Access wiped out tables from original "some.mdb" and left it with it's
original name.
The question is: how Access determines which file contains tables when
"some.mdb" starts?

Many thanks.
Denis.

 

[Jeff Boyce]

If you used the wizard, I would think that it would create "links" to the
..mdb file with the tables.

Have you opened the front-end (the one without the tables) and checked the
tables tab to see if the tables are "linked"?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[dannis]

All tables really became linked and targeted to appropriate tables in
"some_be.mdb".
Thank you.

 

[Albert D. Kallal]

Great question:

It turns out is not done on a SINGLE mdb file,but on a table by table bases.

What this means is that a linked table can be in any databae on your
computer.

And, this means that EACH table could in theory be in a DIFFERENT back end
database.

As a general rule to keep our sanity, we tend to just have ONE data part,
and one appcation part.

I explain the linking process, and how you "change" where the table is
linked to here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

So once a table is linked, them ms-access "remembers" that link until you
change it. This link is done and remembered on a table by table bases. It
also means that if you move the back end, the links are broken, and you
would have to re-link the tables (usually with the linked table manager).