I'm guessing that you have some basic design problems.
(I have fairly complex apps with 100K+ records that are 10-30 megs in
combined file size).
Have you split your database into back-end tables, and front-end app
(forms/reports)? If so, 1 gig is a ton of records. Are the tables
normalized at least to the third level? If you really expect millions of
records, you'll be better off using an enterprise product like SQL or
Oracle.
If your front forms/reports are growing that large, you have big amounts of
embedded graphics that you could link instead. You might also have
repeating form/reports (like a daily report) that can be generalized to a
single report with a variable date.
If none of the above apply, try decompiling the mdb, the re-compiling and
compacting.
-Ed
"Gary" <g4****@hotmail.com> wrote in message
news:42**********************@news.optusnet.com.au ...
Is it much of a problem is an Access database reaches over 1 gig in size?
I
can easily see the database I designed reaching that figure in a few weeks
time. Even with the compacting/repair utility I run every day.