Reached Max Size - New Strategy?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've reached the 2 gig mark because I have a couple large tables and lots of
pictures. Never thought it would happen but here I am...so I need a strategy
to reduce the size of the db without losing any tables. I've already
Compacted. Suggestions on reading material to understand and/or strategies
to reduce???
 
Storing pictures in a database quickly bloats the size of the database file.
Store your pictures in a folder external to the database then store the path
to the pictures in your database. To display the pictures, use an image
control (from toolbox) and set the Picture property to the full path to the
appropriate picture.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)
 
Steve,

I do have a folder external to the table but I use "Insert" -> "Object" ->
etc to give the path to the picture. I have thousands of marinas and usually
insert at least 3 pics for each facility. Is inserting the same as linking?

Thanks.
 
I am not sure what uou mean you use "Insert" -> "Object". Could you describe
and give an example. Off the cuff it seems obvious that inserting takes a
lot of resources smply because your file size is 2 Gig. Could you also
provide the fields for your marina table and any any associated table that
is connected to your pictures.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)
 
Access 2007 is suppose to do a much better job of storing graphic files which
should reduce bloat quite a bit.
 
What resolution are your pictures? If you are storing 8 megapixel pictures
and all you are using them for is viewing on the screen or printing snapshot
size ones you are wasting space. Try reducing the size of the pics to .5
megapixel (800 X 600) or less before you store/link them. Space and time to
view will improve.
Note to all digital photographers:
Just because your camera will shoot 100 megapixel shots doesn't mean that
every picture should be shot at that resolution. Think about the end use and
adjust the size when taking the pic. In most situations .5 to 1.0 megapixels
will suffice.
 
Storing an image in an Access database will bloat the database no matter the
resolution. I don't know if the situation improves with a lower resolution
image, but in any case storing more than a few images will quickly cause the
database to become unacceptably large. As has been stated, Access 2007
handles images better than previous versions. My observation applies to
pre-2007 versions.
Having said that, a lower-resolution linked image has a lot to recommend it,
particularly if it is stored in a network location.
 
Storing an image in an Access database will bloat the database no matter
the

Because a bitmap image is stored with the original image.



BruceM said:
Storing an image in an Access database will bloat the database no matter the
resolution. I don't know if the situation improves with a lower resolution
image, but in any case storing more than a few images will quickly cause the
database to become unacceptably large. As has been stated, Access 2007
handles images better than previous versions. My observation applies to
pre-2007 versions.
Having said that, a lower-resolution linked image has a lot to recommend it,
particularly if it is stored in a network location.
Click to expand...
 
Back
Top