Linked photo files- Is it really this bad?

[salmonella]

It seems that if I have an OLE field and I LINK a photo to it, if it is a
bitmap image, or otherwise is displayed in the forms's field, the database
goes up in size relative to the size of the photo.

If, however, I LINK the field/photo using an icon for the image, the size of
the Db goes up very little, a double click of the field/icon will open the
image..... BUT, I only get an icon for the field on a Report.

Is there a way to show a photo in a report, (or even the form’s field), and
NOT have the database size balloon out of control?


Thanks!

 

[Douglas J. Steele]

The sample imaging databases at http://accdevel.tripod.com illustrate three
approaches to handling images in Access, and the download includes an
article discussing considerations in choosing an approach. Two of the
approaches do not use OLE Objects and, thus, avoid the database bloat, and
some other problems, associated with images in OLE Objects.

If you are printing the images in reports, to avoid memory leakage, you
should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
PrintFailure.zip is an Access97 MDB containing a report that fails during
the Access formatting process prior to being spooled to the Printer Driver.
This MDB also contains code showing how to convert the contents of the Image
control to a Bitmap file prior to printing. This helps alleviate the "Out of
Memory" error that can popup when printing image intensive reports.

If you've already starting storing images in your database, and you'd like
to export them all, see: http://www.lebans.com/oletodisk.htm

 

[salmonella]

Thanks again Doug!

Took a quick look at it and it seems like it will get me started.

Many Thanks!