_PAGENO with MEMO fields
Brian Cleverly
>
>I've been fighting for two days with a wierd problem involving page
>numbers and memo fields. I have a report that prints seven memo
fields,
>each the full width of the page, with the stretch option selected.
Some
>records in my file have large memo fields, resulting in multiple pages
of
>output for those particular records. In the Page Footer band, I am
>attempting to display the page number. Problem is, it appears as
though
>_PAGENO doesn't increment until the record pointer moves. So, in the
case
>of these large records, I end up with two consecutive pages with the
same
>page number. In fact, I've tried creating a variable and
incrementing in
>manually within the page footer. Same result, the footer isn't
refreshed
>until the record pointer moves.
>
>So, what now? This is in 2.6a for Windows. I've tried every trick
that I
>can think of, and can't get this to work. Anyone have any brilliant
>ideas?
>
>Thanks!
Are you re-printing the page header on each new page??
If so, why not temporarily output _pageno in the header and confirm
whther or not it is being incremented correctly.
If it is, then place a UDF field somewhere in the report body. The UDF
should set a public var to = _pageno and return a blank. Then use the
public var in the footer band.
If _pageno doesn't increment correctly then I would need to give the
matter some further thought/experimentation. (love a challenge).
Regards,
Brian Cleverly
None Listed
Brian Cleverly <an...@ix.netcom.com> wrote:
>Are you re-printing the page header on each new page??
>
>If so, why not temporarily output _pageno in the header and confirm
>whther or not it is being incremented correctly.
I have run into this also. I was doing a job for the government, and we
had to print out rather long reports containing various memo fields of
personnel information. Each person in the DBF would generate a "resume"
that was 3 to 6 pages or so of data from various DBF memo fields. We
COULD NOT get the _PAGENO counter to increment properly no matter what we
tried, and we had no option to leave the page number off, so we had to
redo the whole thing with ??? and @...SAY commands, and control the page
number in a variable ourselves.
If anyone does know how to get around this, I would appreciate hearing
about it also.
- John
--
Boulder's Database Experts: http://www.geopages.com/paris/1170
Cy Welch
>>If so, why not temporarily output _pageno in the header and confirm
>>whther or not it is being incremented correctly.
>I have run into this also. I was doing a job for the government, and we
>had to print out rather long reports containing various memo fields of
>personnel information. Each person in the DBF would generate a "resume"
>that was 3 to 6 pages or so of data from various DBF memo fields. We
>COULD NOT get the _PAGENO counter to increment properly no matter what we
>tried, and we had no option to leave the page number off, so we had to
>redo the whole thing with ??? and @...SAY commands, and control the page
>number in a variable ourselves.
>If anyone does know how to get around this, I would appreciate hearing
>about it also.
I'll bet you had the page number at the BOTTOM of the page. I found
that if I put the page number at the TOP of the page, that things
appear to work just fine after that.
--
**************************************************************
* Cy Welch All views are my own *
* cwe...@calweb.com *
* http://www.calweb.com/~cwelch/ Web Page *
**************************************************************
Brian Copeland
T>I've been fighting for two days with a wierd problem involving page
T>numbers and memo fields. I have a report that prints seven memo
T>fields, each the full width of the page, with the stretch option
T>selected. Some records in my file have large memo fields, resulting
T>in multiple pages of output for those particular records. In the Page
T>Footer band, I am attempting to display the page number. Problem is,
T>it appears as though _PAGENO doesn't increment until the record
T>pointer moves. So, in the case of these large records, I end up with
T>two consecutive pages with the same page number. In fact, I've tried
T>creating a variable and incrementing in manually within the page
T>footer. Same result, the footer isn't refreshed until the record
T>pointer moves.
T>So, what now? This is in 2.6a for Windows. I've tried every trick
T>that I can think of, and can't get this to work. Anyone have any
T>brilliant ideas?
T>Thanks!
I have printed reports where a single memo field has ran as much as 10
pages without any problems with page numbering.
Are you calling and UDFs in the report that might be resetting _pageno?
Are the page header and footer printing properly on each page?
Brian.C...@canrem.com (Brian Copeland)
David J. Grenier
> I've been fighting for two days with a wierd problem involving page
> numbers and memo fields. I have a report that prints seven memo fields,
> each the full width of the page, with the stretch option selected. Some
> records in my file have large memo fields, resulting in multiple pages of
> output for those particular records. In the Page Footer band, I am
> attempting to display the page number. Problem is, it appears as though
> _PAGENO doesn't increment until the record pointer moves. So, in the case
> of these large records, I end up with two consecutive pages with the same
> page number. In fact, I've tried creating a variable and incrementing in
> manually within the page footer. Same result, the footer isn't refreshed
> until the record pointer moves.
>
> So, what now? This is in 2.6a for Windows. I've tried every trick that I
> can think of, and can't get this to work. Anyone have any brilliant
> ideas?
I had a similar problem, but not with MEMO fields. My problem revolves
around FP not updating _PAGENO when the only thing in the last page is a
Group Footer or Summary. I got around this by putting _PAGENO in the Page
Header. It appears FP is a little too selective about when it regenerates
the Page Footer. Hope this helps.