Database bloat with linked .JPG's

[Michael F.]

When I link a JPG to a table as an OLE object, the
database increases in size by 2-4X the size of the JPG.
For example, if I link to a 100K jpg, the database expands
by 400K. If I link to a 1400K jpg, the database goes from
700K to over 6M.
The basic problem will soon be that my database will get
over the 2G limit. Even if I split it and put the jpg's
alone in their own MDB, they will reach 2G too. For
reference, I'm using Access 2000 format.

 

[Van T. Dinh]

I believe that when you store graphics in Access, Access will convert these
to .bmp before storing.

Basically, Access / JET is inefficient in storing graphics. Don't store
graphics as an OLE Field. Store your graphic files separately and simply
store the paths to these files in the database.

 

[Michael F.]

Thanks for the reply. However, what will the actual link
look like in a table? Right now, the table has a key field
and the OLE field. Will it now have a text field in place
of the OLE field with a full path as the contents?

Mike

 

[Van T. Dinh]

Yes. Just the full-path name (or relative path name) of the JPG files as
Text Field values and use code to control / show the image when required.