newbie help

[steve]

(sorry by mistake it was originally posted in a thread)

Hi all,
I was just wondering:

1) Is it OK if someone creates a few .mdb files in order to avoid the
Access size limitations ? I am supposed to be updating an old database and i
still try to figure out why there are multiple .mdb files. I know for a fact
that they were not created at a later day as some people in this nwesgroup
have suggested. By the way WHY ? Why would you create other .mdb files if
you wanted to expand/add/modify a databse, and not simply add more
forms/tables?

2) (related to the first question) Is it easy to "link" a couple of .mdb
files together. I mean is easy in e.g. main.mdb to create a query and output
that links together info from tables that exist in db1.mdb, db2.mdb, etc.
???

Thanx in advance

 

[John Vinson]

(sorry by mistake it was originally posted in a thread)

Not really a problem - it shows up as a new message anyway (and
depending on newsreader: in this case both messages were in the same
thread). It may help to have a more informative Subject though ("Why
multiple mdb's" perhaps!)

Hi all,
I was just wondering:

1) Is it OK if someone creates a few .mdb files in order to avoid the
Access size limitations ? I am supposed to be updating an old database and i
still try to figure out why there are multiple .mdb files. I know for a fact
that they were not created at a later day as some people in this nwesgroup
have suggested. By the way WHY ? Why would you create other .mdb files if
you wanted to expand/add/modify a databse, and not simply add more
forms/tables?

Hard to read the mind of the original developer but size (1 GByte with
A97) may indeed have been an issue.

2) (related to the first question) Is it easy to "link" a couple of .mdb
files together. I mean is easy in e.g. main.mdb to create a query and output
that links together info from tables that exist in db1.mdb, db2.mdb, etc.
???

It is in fact possible, with some limitations. You cannot create a
relationship with relational integrity enforced across .mdb's, only
within a single .mdb; you can, however, create a Query linking a table
in one backend with a table in another one. Performance will probably
be markedly slower. As suggested elsethread, if you're pushing the 2
GByte limit, it's time to be looking at client-server architecture
anyway!