Ole Objects in a form

  • Thread starter Thread starter Kathy Zallar
  • Start date Start date
K

Kathy Zallar

My Acess database is approx. 1.9 meg. I added a picture
field to the table as an Ole Object. I inserted this into
my form...great so far. Inserted a jpeg pic, worked great.
BUT it bloated my DB from 1.9 Meg to 7 meg. The pic I
inserted was only 40kb.....what is causing this. I
compacted and still stayed huge. After adding just 4 pics
I was up to 25 meg...Please Help

Kathy
 
Kathy Zallar said:
My Acess database is approx. 1.9 meg. I added a picture
field to the table as an Ole Object. I inserted this into
my form...great so far. Inserted a jpeg pic, worked great.
BUT it bloated my DB from 1.9 Meg to 7 meg. The pic I
inserted was only 40kb.....what is causing this. I
compacted and still stayed huge. After adding just 4 pics
I was up to 25 meg...Please Help
Click to expand...

Storing pictures in your database, while supported is not really practical. The size
bloat you're seeing is completely normal. A compressed image format like jpeg are
converted to full size bmp and that is what is stored in addition to some OLE
overhead and I believe a thumbnail copy as well.

The usual recommendation is to store your images as separate files and only store the
path to them in your database. You can use an image control to display the images in
a form or report by setting its Picture property to the path string you saved.
 
OLE Embedding causes an uncompressed image to be stored in the table that can be 10 to 100 *times* the size
of the original file.

If you want to store the images actually in the database you should store them as raw-binary/blob data,
then they use just the same space as the original file.
 
How do I do that????? I am a rookie at this...
-----Original Message-----

OLE Embedding causes an uncompressed image to be stored
Click to expand...
in the table that can be 10 to 100 *times* the size
of the original file.

If you want to store the images actually in the database
Click to expand...
you should store them as raw-binary/blob data,
 
Back
Top