However if you choose to split the data into multiple Access (Jet or ACE)
backends you can in theory have really large databases (up to 2 gigabytes
for each of the linked backends). I suspect that the performance could
(probably would) be terrible if you needed to do this.
Not as bad as one would think. In the huge 30 GB Access 2.0 database I once
worked on, a list box selection named the table, and a record could be
retrieved in a few seconds.
In an Access 2003 database with 2, 1+ GB backends, joined with a union
query. A record could be retrieved from over 12 million rows in about 20
seconds. Considering that it had to completely run the union query first,
that isn't too bad.