CurtainMary said:
Thanks for coming back Larry. Each report has the logo
as an image control. Because the database is devolped on
another computer and there are other copies (updated 3
monthly) it wouldn't be feasible to use an external linked
file for the logo.
I will give it up.
Thank you for your trouble.
Mary
Perhaps all is not lost, Mary.
Take a look at the example referenced in the following. I don't see why you
could not use the BLOB technique to distribute the database, but instead of
unBLOBing to a temporary file for each use, write it to an image file in the
same folder as the database the first time a new copy of the database is
used. Then, if you try to use that image and find it's not there... either
deleted, or the database has been moved, just create a new one in the same
folder as the database.
Or, if you've got lots of processing power on your machines, you could just
use the technique as shown, only in the OnPrint event of the Report's
Section where the picture is to be displayed, instead of the OnCurrent event
of a Form, as demonstrated.
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