By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,613 Members | 1,890 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,613 IT Pros & Developers. It's quick & easy.

Database Size

P: n/a
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.

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
The 1 gig limit applies to Access 97 the limit on later versions is 2
gig. However, because your database can include linked tables in other
files, its total size is limited only by available storage capacity.

Nov 13 '05 #2

P: n/a
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.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.