Why OLE requires additional software and adds bitmap files.

[Guest]

I want to put photographs in an access database and I cant figure out how.
THe above topice will not print out from "Use of images in your Access
forms.........."

 

[Larry Linson]

I want to put photographs in an access database
and I cant figure out how.
THe above topice will not print out from "Use of images in
your Access forms.........."

Object Linking and Embedding (OLE) is a mechanism for using OLE-compliant
applications registered in your system for particular image file types to
open them for viewing or editing. By definition, it requires additional
software.

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.

Larry Linson
Microsoft Access MVP

 

[Guest]

Object Linking and Embedding (OLE) is a mechanism for using OLE-compliant
applications registered in your system for particular image file types to
open them for viewing or editing. By definition, it requires additional
software.

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.

Larry Linson
Microsoft Access MVP