Report including pictures

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

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 of
data in the table (filtered))?

Thanks,
J.
 
Jason said:
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 of
data in the table (filtered))?
Click to expand...

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

And, Stephen has an ActiveX control available that works in cases where the
graphics filters are not available -- and works better, I've heard, than the
OLE Object and OLE Controls.

Please note that there are other approaches, e.g.,
Application.FollowHyperlink, but those, like OLE and Bound OLE Frames (which
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. But,
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. It
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
 
Using Access 97
Larry Linson said:
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 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.

And, Stephen has an ActiveX control available that works in cases where the
graphics filters are not available -- and works better, I've heard, than the
OLE Object and OLE Controls.

Please note that there are other approaches, e.g.,
Application.FollowHyperlink, but those, like OLE and Bound OLE Frames (which
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. But,
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. It
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
Click to expand...
 
These only show forms - there are no reports!
Larry Linson said:
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 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.

And, Stephen has an ActiveX control available that works in cases where the
graphics filters are not available -- and works better, I've heard, than the
OLE Object and OLE Controls.

Please note that there are other approaches, e.g.,
Application.FollowHyperlink, but those, like OLE and Bound OLE Frames (which
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. But,
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. It
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
Click to expand...
 
Jason said:
These only show forms - there are no reports!
Click to expand...

That's correct -- did you read the text? It explains what is different
about doing similar display in reports, and refers you to Stephen Lebans'
examples in regard to report. If you can't make that leap, then you
probably need more help than you can get from my simple examples and
Stephens'. I do not, unfortunately, know of a self-study book with extensive
coverage in this area.

Several other people who post here do have examples... Arvin Meyer is one
who comes immediately to mind.

My examples were intended to help you understand learn how to handle
images -- they are not intended to be copied and pasted into an application,
and be able to work without change. No matter how much people may want them,
copy-and-paste-and-use examples are normally either not possible, or very
difficult to create.

Larry Linson
Microsoft Office Access MVP
 
I've had to (for every picture added or changed)
Use VBA
create a new form that is opened (with the associated table) from the form I
use
update the fields including the OLEobject
close the form
Now I can use that table as part of the report and include OLE object on the
report. So now Access is inflated since the image is installed in Access
file as well as a JPG file. One thing I could look at is using this form to
view the full picture (actually only 12x9cm) and then double click on the
picture which only opens MS editor - but then covers most of the screen
without learning how to get screen resolution and form size just by using
zoom and maximize.

Took a bit to work out - by stepping through the vba on the + button. I
don't know how I can do it without using a table without the OLEobject.
 
Back
Top