Are the photos actually being stored in the database? If so, that's the
problem: prior to Access 2007, Access was very inefficient with storing
binary information.
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
--
Doug Steele, Microsoft Access MVP
(no private e-mails, please)
"Leah with Firestorm W.F.S. Inc."
