Split Database

P

PeterM

Our .mdb file size is getting sizable. Is there a way to split the current
..mdb into smaller .mdb's keeping in mind that forms are called passing
openargs in the docmd.open call to forms.

Thanks in advance for your help!
 
D

Douglas J. Steele

All of the "application" (the queries, forms, reports, macros and modules)
should be in one database. It's best if all of the tables are also in one
database (since otherwise you can't enforce referential integrity through
relationships), but it's possible to have the data in more than one backend.
 
J

John Vinson

Our .mdb file size is getting sizable. Is there a way to split the current
.mdb into smaller .mdb's keeping in mind that forms are called passing
openargs in the docmd.open call to forms.

Thanks in advance for your help!
Click to expand...

You've Compacted the database I hope? And how big is "sizeable" -
approaching 2 GByte (the limit of Access)?

It is possible to use a "split" database with the data tables in one -
or more - backend database(s) and the forms, reports, code etc. in a
frontend; for a multiuser database this is pretty much essential. If
you haven't split in this way, DO SO; if you have, which database is
bloating - the frontend or the backend?

John W. Vinson[MVP]
 
P

PeterM

I setup the database to compact on closing so it's always as small as
possible. I'm talking exclusively about the frontend. The back end tables
are hosted on an ISP and we use ODBC to get to the tables. It's actually
pretty fast and the users seem pleased with response times.

Maybe I'm paranoid, but the .mdb is now over 40meg. I know I'm not anywhere
near the 2gig size limit of Access, but when I publish updates to the forms,
reports, etc I have to FTP them manually to the ISP server and that takes 30
minutes to copy both the .mdb and .mde (which is slightly smaller). I'm
using Ac2002.

I was just hoping to be able to split the front end into pieces, that way I
could keep file sizes smaller and reduce upload/download times. From what I
understand, this is not possible...correct?
 
J

John Vinson

I setup the database to compact on closing so it's always as small as
possible. I'm talking exclusively about the frontend. The back end tables
are hosted on an ISP and we use ODBC to get to the tables. It's actually
pretty fast and the users seem pleased with response times.
Click to expand...

ok... that's excellent.
Maybe I'm paranoid, but the .mdb is now over 40meg. I know I'm not anywhere
near the 2gig size limit of Access, but when I publish updates to the forms,
reports, etc I have to FTP them manually to the ISP server and that takes 30
minutes to copy both the .mdb and .mde (which is slightly smaller). I'm
using Ac2002.
Click to expand...

<chuckle> One of my current main client's frontend databases is now
some ten times larger than yours. (It has some graphics in it is
probably why, though it's BIG).
I was just hoping to be able to split the front end into pieces, that way I
could keep file sizes smaller and reduce upload/download times. From what I
understand, this is not possible...correct?
Click to expand...

One thing you can consider is creating a .mda Library database (or
more than one) for shared code and forms. I haven't actually done this
in real life though so I'm not the best person to ask!

John W. Vinson[MVP]
 
Top