images in reports ... only drawn sometimes

[NASAdude]

I'm working on a report that shows a lot of data, so I've set it up so
it is 2-pages wide in landscape view for each record. ie: The report
is 22" wide (less margins). On the left page there are three images,
and there are two images on the right page. The images are stored in
a directory, and only path\filename info is stored in the database.
For testing purposes, there are only four records, so there isn't a
memory issue.

I'm using the Me.ImageX.Picture=<path\file> technique in the
Detail_Print event. The report works ok except that the two images on
the right-side page don't appear. If I drag one of the working three
images from the left side to the right side, it doesn't work either.
No code is changed; just moving the object makes it not be drawn.
There are no error messages. It seems that because the images are on
a non-visible page when the event is run they aren't being drawn, even
though the Detail_Print even does cycle through all five images.

Also, printing directly to PDF (w/o 'previewing') also doesn't show
the right-hand images.

As a secondary question (perhaps another thread), has anyone noticed
objects to be jumpy as to where they appear in a report in print
preview? In design view, I move an object one grid square to tweak
the appearance, but in print preview the item jumps more than half an
inch. It only happens at certain locations in the report. It's an
odd problem that I've never seen before in reports over the last two
years of working with Access.

System: WinXP Pro, OfficeXP Pro

[Eric Ellsworth]

NASAdude wrote:

I'm working on a report that shows a lot of data, so I've set it up so
it is 2-pages wide in landscape view for each record. ie: The report
is 22" wide (less margins). On the left page there are three images,
and there are two images on the right page. The images are stored in
a directory, and only path\filename info is stored in the database.
For testing purposes, there are only four records, so there isn't a
memory issue.

I'm using the Me.ImageX.Picture=<path\file> technique in the
Detail_Print event. The report works ok except that the two images on
the right-side page don't appear. If I drag one of the working three
images from the left side to the right side, it doesn't work either.
No code is changed; just moving the object makes it not be drawn.
There are no error messages. It seems that because the images are on
a non-visible page when the event is run they aren't being drawn, even
though the Detail_Print even does cycle through all five images.
What happens if you drop the images directly in the report w/o loading
them dynamically? I guess what I'm suggesting is an ugly hack where you
could modify the Report's design programmatically before running it? I
guess that wouldn't work if the images vary with the detail.
Also, printing directly to PDF (w/o 'previewing') also doesn't show
the right-hand images.

As a secondary question (perhaps another thread), has anyone noticed
objects to be jumpy as to where they appear in a report in print
preview? In design view, I move an object one grid square to tweak
the appearance, but in print preview the item jumps more than half an
inch. It only happens at certain locations in the report. It's an
odd problem that I've never seen before in reports over the last two
years of working with Access.

I've definitely seen all kinds of weird rendering tricks when the report
is previewed - clipping, moving, jumping, so I'm not too surprised the
preview's a little ugly, but in my experience those things are usually
resolved when you actually print it. Have you been able to run the
report printing directly to a printer?
Hope some of this helps,

Eric

[NASAdude]

Nevermind.

Yes, there is still a bug in how Access draws images changed in the
Detail_Print event for two-page wide reports.

I fixed the problem by making the report two pages tall. Now the
Detail_Print event is called twice, once for each portion of the
Detail section. I simply edited the code to process images 1-3 the
first time through and 4-5 the second time through, using (me.page mod
2 = 0) as the test condition. I also had to use a similar trick on
the report header and footer.

Also, the other problem I mentioned is fixed. I think the jumpiness
of objects was related to the CanGrow properties. ie: objects on the
right page were resizing slightly, which affected the positioning of
things on the left page. The top/bottom page approach fixed that.

Hopefully this will end up helping someone else.