To Marsh Barton: Addressing seperate pages on a report (additional problem)

[Marcel Stoop]

Hi marsh

Like I said, it was just what I was looking for.

There is only one problem left.
In some situations Me.txtX contains only 1 Value. In those situation the
report will only be 1 or 2 page long.
If that happens (Me.txtX contains only 1 Value), Me.txtY gets invisible,
which should not happen.
In this situation Me.txtY should be visible.

Any idea how I can fix this problem.

Thanks again for the help

 

[Guest]

You can check the 'pages' property of the report. If pages = 1 or 2,
ignore your other code and just set me.txty visible.

I think you need to display the 'pages' property on your report to
get it to calculate correctly. (normally with a text box control
= [page] & " of " & [pages]

(david)

 

[Marshall Barton]

The Nz(Me.txtZ, "junk")) was supposed to take care of that.

The only thing I can think of that would cause that effect
is if you have a text box that references the Pages
property. In that case the last value in txtZ would match
the first txtX. The way I think would try to deal with it
is to use the report header section's Format event to set
txtZ to Null (or any nonsense value).

 

[Marcel Stoop]

Thanks to the both of you

I will try both solutions and will let you know how it worked

Thaqnks again
Cheers
Marcel

The Nz(Me.txtZ, "junk")) was supposed to take care of that.

The only thing I can think of that would cause that effect
is if you have a text box that references the Pages
property. In that case the last value in txtZ would match
the first txtX. The way I think would try to deal with it
is to use the report header section's Format event to set
txtZ to Null (or any nonsense value).
--
Marsh
MVP [MS Access]

Like I said, it was just what I was looking for.

There is only one problem left.
In some situations Me.txtX contains only 1 Value. In those situation the
report will only be 1 or 2 page long.
If that happens (Me.txtX contains only 1 Value), Me.txtY gets invisible,
which should not happen.
In this situation Me.txtY should be visible.

Any idea how I can fix this problem.

 

[Marcel Stoop]

Thanks Marsh

You were right, I have a text box that references the pages.
Your solution solved the Problem

Thanks Again

Cheers
Marcel

The Nz(Me.txtZ, "junk")) was supposed to take care of that.

The only thing I can think of that would cause that effect
is if you have a text box that references the Pages
property. In that case the last value in txtZ would match
the first txtX. The way I think would try to deal with it
is to use the report header section's Format event to set
txtZ to Null (or any nonsense value).
--
Marsh
MVP [MS Access]

Like I said, it was just what I was looking for.

There is only one problem left.
In some situations Me.txtX contains only 1 Value. In those situation the
report will only be 1 or 2 page long.
If that happens (Me.txtX contains only 1 Value), Me.txtY gets invisible,
which should not happen.
In this situation Me.txtY should be visible.

Any idea how I can fix this problem.