File Size Limitations

  • Thread starter Thread starter Scott Wise
  • Start date Start date
S

Scott Wise

Does anyone know if Access 2000 removes the 1 gigabyte
file size restriction present in Access97?

We currently use Access97 for our reports, and our file
size is already 400MB.
 
Scott Wise said:
Does anyone know if Access 2000 removes the 1 gigabyte
file size restriction present in Access97?

We currently use Access97 for our reports, and our file
size is already 400MB.
Click to expand...

Access 2000 increases the maximum .mdb file size to 2GB, but since it
stores text as unicode that isn't the doubling of capacity that you may
think. With unicode compression, though, you do get more practical
storage space than you had before -- I just don't know how much.

Have you compacted your database recently? 400MB is still a workable
size in Access 97, but maybe a lot of that is unrecovered space.
 
I compact the database approximately once a week.

I knew that our file size was going to increase
dramatically when we started inserting linked pictures in
the jpeg format into our reports. The pictures are not
inserted on a daily basis, but I think that Access still
allocates the space in the database record for the images.
 
Scott Wise said:
I compact the database approximately once a week.

I knew that our file size was going to increase
dramatically when we started inserting linked pictures in
the jpeg format into our reports. The pictures are not
inserted on a daily basis, but I think that Access still
allocates the space in the database record for the images.
Click to expand...

As John Vinson noted, storing images in your database will vastly
increase its size. Even the compressed JPEG format does, because Access
stores a bitmap version of the picture. I'm not sure from what you say
whether you're already doing this or not, but it's better to store only
the path to the image file, and use an appropriate event to set the
Picture property of an unbound image control to that path.
 
Yeah, I already do this. Thanks for the help.

-----Original Message-----
images.

As John Vinson noted, storing images in your database will vastly
increase its size. Even the compressed JPEG format does, because Access
stores a bitmap version of the picture. I'm not sure from what you say
whether you're already doing this or not, but it's better to store only
the path to the image file, and use an appropriate event to set the
Picture property of an unbound image control to that path.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.
Click to expand...
 
Unfortunately, we now have to include photographs in some
of our reports (investigations, damages, and legal
issues).
Click to expand...

Check back with Dirk's links. It is perfectly possible to include
photographs in your *reports* without storing the image data within
your *database*. Store the .jpg file separately, on disk, and store
only a path and filename, or a Hyperlink, in a text field in your
table; and obtain some of the simple VBA code that's available at the
cited links to display the selected image on the report.
 
John Vinson said:
Check back with Dirk's links. It is perfectly possible to include
photographs in your *reports* without storing the image data within
your *database*. Store the .jpg file separately, on disk, and store
only a path and filename, or a Hyperlink, in a text field in your
table; and obtain some of the simple VBA code that's available at the
cited links to display the selected image on the report.
Click to expand...

I don't think I posted any links in this thread -- that was a different
thread -- but if I had, I'd probably have posted this link to Larry
Linson's page on images in Access

http://accdevel.tripod.com/imaging.htm:
 
inserted on a daily basis, but I think that Access still
allocates the space in the database record for the images.
Click to expand...

?? I would be surprised - I would expect Access to allocate
a pointer to a separate area - like it does for a memo field.

(david)
 
Back
Top