> "Jason" <JAllenNZ@hotmail.com> wrote
>
>  > I ahve a table that has path of photo with form_oncurrent and
>  > parth_afterupdate displaying the picture. How can I get the picture to
> show
>  > on the report (the report would be prety small compared to the amount

>  > data in the table (filtered))?
>
> The Report Events corresponding to a Form's OnCurrent would be Format or
> Print. Just for efficiency, I tend to use the Print event, because Format
> may fire multiple times for a given Record.
>
> The sample imaging databases at http://accdevel.tripod.com illustrate

> 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'

> PrintFailure.zip is an Access97 MDB containing a report that fails during
> the Access formatting process prior to being spooled to the Printer

> This MDB also contains code showing how to convert the contents of the

> control to a Bitmap file prior to printing. This helps alleviate the "Out

> Memory" error that can popup when printing image intensive reports.
>
> And, Stephen has an ActiveX control available that works in cases where

> graphics filters are not available -- and works better, I've heard, than

> OLE Object and OLE Controls.
>
> Please note that there are other approaches, e.g.,
> Application.FollowHyperlink, but those, like OLE and Bound OLE Frames

> from the symptoms you describe, are what you were / are using) still leave
> you "at the mercy of the imaging software registered for the filetype").
>
> Finally, Access 2007 has enhancements that, reputedly, eliminate the
> database bloat long associated with OLE Objects and Bound OLE Frames.

> it still leaves you relying on the software registered for the image type,
> which may not be as "cooperative" as we'd like in creating our display.

> also has the capability of having a variable number of Attachments to a
> Record, which may be helpful.  But, as I have not done much with it yet, I
> certainly wouldn't suggest you rush out and replace an earlier version --
> until you have a copy incorporating, at least, the first Service Pack, or
> have
> the SP in hand and ready to apply as soon as you install Access 2007.
>
>  Larry Linson
>  Microsoft Office Access MVP