Back-end database

[Mike]

I have a database which consists of a front-end and a back-
end database. I would like to know if it is better to
store all tables in one back-end database or to save each
table in a separate database. Which way can increase
stability?
Thank you in advance!

 

[Duane Hookom]

I would place them all in a single MDB. This would allow you to create and
maintain referential integrity.

 

[John Vinson]

I have a database which consists of a front-end and a back-
end database. I would like to know if it is better to
store all tables in one back-end database or to save each
table in a separate database. Which way can increase
stability?
Thank you in advance!

Unless you have a VERY good reason to use multiple backends (say you
have several tables all of which are approaching 2 GByte in size), use
just one backend. It's simpler, faster, more stable, and it lets you
maintain relational integrity between the tables; you cannot establish
relational integrity across different .mdb files.

 

[TC]

Are you thinking of dBase? In dBase, a "database" was what everyone else
would call a "table". So, in dBase, the data was stored in many "databases".
In Access, a "database" is the whole collection of tables & related items.
You store all your Access tables in a single Access database, unless there
is good reason not to.

HTH,
TC