Access database is 2gb

[tom]

My access database is already 2Gigabytes after only
22,000 records and we are getting invalid argument when
we try to do anything. I think it is so large because
one of the fields includes a scanned document that must
be a scanned file.

what are the best options with out deleted the oldest
records since we would like this in ONE DAtabase for at
least a years worth of data???

thanks,
tom

 

[Lynn Trapp]

Storing images in the database can definitely cause significant bloating.
You should, instead, store the path to the image file and use code to
display the image on a form or report when you need it. The Northwind
database has a good example of how to do this on the Employee form.

 

[Larry Linson]

My access database is already 2Gigabytes after only
22,000 records and we are getting invalid argument when
we try to do anything. I think it is so large because
one of the fields includes a scanned document that must
be a scanned file.

what are the best options with out deleted the oldest
records since we would like this in ONE DAtabase for at
least a years worth of data???

In addition to Lynn's suggestion... a very apt one... you said nothing about
having ever compacted the database -- Access does not retrieve vacated space
until you do. But, if you have 22,000 scanned documents stored in OLE
Objects, you could be approaching the limit even if you do regularly
compact.

Take a look at the samples on http://accdevel.tripod.com, which illustrate
three approaches to handling images in Access, which may explain the
"bloat", but two of the approaches do not have the same kind of bloat.

Larry Linson
Microsoft Access MVP