Hello,

I have a report that has only 2 levels of grouping.
The detail section is simply 1 large block for a memo field.

I am finding that on some occasions the report errors and generates hundreds
(perhaps even an infinite loop...I have to break the system to stop the
report generating) of pages.

While I'm not 100% I think this may have something to do with the detail
section (memo field) running over to 2 pages.

The Detail section itself is set to YES for Can grow and Can shrink.
The memo field control is also set to YES for Can grow and Can shrink.

In the Sorting and Grouping I have turned off the KEEP TOGETHER property for
now.

The report itself gathers messages sent to a particular site (first grouping
level) and then groups messages sent to a single person(second grouping
level).
The can grow/shrink is so I can get many varying length messages on as few
pages as possible.

Any ideas or thoughts would be greatly appreciated.

Mal Reeve wrote:
> Hello,
>
> I have a report that has only 2 levels of grouping.
> The detail section is simply 1 large block for a memo field.
>
> I am finding that on some occasions the report errors and generates hundreds
> (perhaps even an infinite loop...I have to break the system to stop the
> report generating) of pages.
>
> While I'm not 100% I think this may have something to do with the detail
> section (memo field) running over to 2 pages.
>
> The Detail section itself is set to YES for Can grow and Can shrink.
> The memo field control is also set to YES for Can grow and Can shrink.
>
> In the Sorting and Grouping I have turned off the KEEP TOGETHER property for
> now.
>
> The report itself gathers messages sent to a particular site (first grouping
> level) and then groups messages sent to a single person(second grouping
> level).
> The can grow/shrink is so I can get many varying length messages on as few
> pages as possible.
>
> Any ideas or thoughts would be greatly appreciated.
>
>
The times that I've had blank pages is when my report and print margins
conflict. It will print some data and then a blank page, data, blank
page, etc.

I would think that before you solve this problem you do a few print
previews first.

You can get an infinite format loop if you set a header section
to not visible in code.

put a code counter in the format event so that you can break
if you get an infinite loop.

use the hide and skip methods to go past the problem if necessary.

(david)

"Mal Reeve" <mal_lori [at] hotmail.com> wrote in message
news:tCKxg.3342$gF6.2661 [at] newsread2.news.pas.earthlink.net...
> Hello,
>
> I have a report that has only 2 levels of grouping.
> The detail section is simply 1 large block for a memo field.
>
> I am finding that on some occasions the report errors and generates
> hundreds (perhaps even an infinite loop...I have to break the system to
> stop the report generating) of pages.
>
> While I'm not 100% I think this may have something to do with the detail
> section (memo field) running over to 2 pages.
>
> The Detail section itself is set to YES for Can grow and Can shrink.
> The memo field control is also set to YES for Can grow and Can shrink.
>
> In the Sorting and Grouping I have turned off the KEEP TOGETHER property
> for now.
>
> The report itself gathers messages sent to a particular site (first
> grouping level) and then groups messages sent to a single person(second
> grouping level).
> The can grow/shrink is so I can get many varying length messages on as few
> pages as possible.
>
> Any ideas or thoughts would be greatly appreciated.
>

Thanks,

I think I could skip the problem - but how do I determine if it is going to
happen.

Basically - how do I determine if this next instance of the detail will flow
over to another page?

And (for the sake of the reply from Salad) this is not an every other page
type of thing...everything will be good for mny pages, then one particular
record will cause the loop.

I have experimented and found that if I shink the font size enough (varies
on the memo length) it will print just fine. Problem there is I will never
know how much space is left at the bottom of the page.

Thanks,
Mal.

"david epsom dot com dot au" <david [at] epsomdotcomdotau> wrote in message
news:44c81b7a$0$49289$c30e37c6 [at] lon-reader.news.telstra.net.. .
> You can get an infinite format loop if you set a header section
> to not visible in code.
>
> put a code counter in the format event so that you can break
> if you get an infinite loop.
>
> use the hide and skip methods to go past the problem if necessary.
>
> (david)
>
> "Mal Reeve" <mal_lori [at] hotmail.com> wrote in message
> news:tCKxg.3342$gF6.2661 [at] newsread2.news.pas.earthlink.net...
>> Hello,
>>
>> I have a report that has only 2 levels of grouping.
>> The detail section is simply 1 large block for a memo field.
>>
>> I am finding that on some occasions the report errors and generates
>> hundreds (perhaps even an infinite loop...I have to break the system to
>> stop the report generating) of pages.
>>
>> While I'm not 100% I think this may have something to do with the detail
>> section (memo field) running over to 2 pages.
>>
>> The Detail section itself is set to YES for Can grow and Can shrink.
>> The memo field control is also set to YES for Can grow and Can shrink.
>>
>> In the Sorting and Grouping I have turned off the KEEP TOGETHER property
>> for now.
>>
>> The report itself gathers messages sent to a particular site (first
>> grouping level) and then groups messages sent to a single person(second
>> grouping level).
>> The can grow/shrink is so I can get many varying length messages on as
>> few pages as possible.
>>
>> Any ideas or thoughts would be greatly appreciated.
>>
>
>

Mal Reeve wrote:

> And (for the sake of the reply from Salad) this is not an every other page
> type of thing...everything will be good for mny pages, then one particular
> record will cause the loop.

What happens if you print the report for just the record with a memo
that creates the problem? Does that error too?

What happens if you preview the report?

Does this occur everytime for the same record or will it work one time
with the record and othertimes not?

What would happen if you created a report with just the ID and Memo
field and then inserted this as a subreport into the current report,
removed the current memo field, and then linked the subreport to the
main report's ID?

What would happen if you created an extra column in the recordsource like
ExtraColumn : 1
and then put that in detail band and made the field hidden?

What is the setting for KeepTogether for your various bands? See if
changing that makes a difference.


>
> I have experimented and found that if I shink the font size enough (varies
> on the memo length) it will print just fine. Problem there is I will never
> know how much space is left at the bottom of the page.
>
> Thanks,
> Mal.
>
> "david epsom dot com dot au" <david [at] epsomdotcomdotau> wrote in message
> news:44c81b7a$0$49289$c30e37c6 [at] lon-reader.news.telstra.net.. .
>
>>You can get an infinite format loop if you set a header section
>>to not visible in code.
>>
>>put a code counter in the format event so that you can break
>>if you get an infinite loop.
>>
>>use the hide and skip methods to go past the problem if necessary.
>>
>>(david)
>>
>>"Mal Reeve" <mal_lori [at] hotmail.com> wrote in message
>>news:tCKxg.3342$gF6.2661 [at] newsread2.news.pas.earthlink.net. ..
>>
>>>Hello,
>>>
>>>I have a report that has only 2 levels of grouping.
>>>The detail section is simply 1 large block for a memo field.
>>>
>>>I am finding that on some occasions the report errors and generates
>>>hundreds (perhaps even an infinite loop...I have to break the system to
>>>stop the report generating) of pages.
>>>
>>>While I'm not 100% I think this may have something to do with the detail
>>>section (memo field) running over to 2 pages.
>>>
>>>The Detail section itself is set to YES for Can grow and Can shrink.
>>>The memo field control is also set to YES for Can grow and Can shrink.
>>>
>>>In the Sorting and Grouping I have turned off the KEEP TOGETHER property
>>>for now.
>>>
>>>The report itself gathers messages sent to a particular site (first
>>>grouping level) and then groups messages sent to a single person(second
>>>grouping level).
>>>The can grow/shrink is so I can get many varying length messages on as
>>>few pages as possible.
>>>
>>>Any ideas or thoughts would be greatly appreciated.
>>>
>>
>>
>
>