Great, Ill google it and see if I come up with anything!! Its for a college
project and my customer wants all the information i stored in seperate
databases. Personally I think seperate tables will do but i will look it up
and see if I can get it to work!
The user may very well have the mistaken impression that a "table" and
a "database" are two names for the same thing. This is very common for
people with experience in other programs such as dBase or Paradox,
where each table is stored as a separate file, often called a
"database". You may need to explain to this user that Access is
different, and that a "Database" in Access jargon is simply a
container for multiple tables.
You can link to different backends, but as noted, you CANNOT enforce
relational integrity between tables in different databases. This is a
major drawback! In addition, performance and complexity of maintenance
will both suffer.
If the user is concerned about the overall size of the tables,
reassure them that Access has a limit of 2 GByte in any one database,
and that 1,500 MByte databases are quite practical and in routine use.
They might be under the assumption that "10,000 records is awfully big
for one database" - it's not, that's tiny.
John W. Vinson[MVP]
