Split tables

[Jpetrachkoff]

Can someone advise me of the most efficient method to split the table
mdb. Should the data reside in one mdb or is it permitted for the data
to reside in numerous mdb that would be accessed from a singular main
menu. I have split the tables into two mdbs on the same server but the
end users are having diffculties when getting data from the second mdb
table. Seems Access is stopping giving a disk or network error message
when switching mdbs. Network connections have been checked, new hub and
new server.

 

[Douglas J Steele]

Usually it's best to keep all the tables in the same MDB file, unless that's
going to exceed the 2 Gb limit. When your tables aren't in the same physical
file, you can't take advantages of relationships to enforce referential
integrity (or allow cascade deletes or updates, should you want to use those
features)

 

[Joseph Meehan]

Can someone advise me of the most efficient method to split the table
mdb. Should the data reside in one mdb or is it permitted for the data
to reside in numerous mdb that would be accessed from a singular main
menu. I have split the tables into two mdbs on the same server but the
end users are having diffculties when getting data from the second mdb
table. Seems Access is stopping giving a disk or network error message
when switching mdbs. Network connections have been checked, new hub
and new server.

Each situation is different.

In general all the data that is shared should be in the back end on the
server. All else (forms, reports queries etc.) should be on the front ends
located on each user's machine. Some static data may be in a table on each
user's machine.

The split table wizard may help you.