RepeatSection Bug question

[david epsom dot com dot au]

Does anyone know or suspect anything extra about the RepeatSection bug?
(that causes a report to hang if you have a section with .visible = false
and .RepeatSection = True) I notice that as I go through the sections
making some visible and some invisible, the report only sometimes hangs. Is
that predictable in any way?

(david)

 

[Marshall Barton]

Does anyone know or suspect anything extra about the RepeatSection bug?
(that causes a report to hang if you have a section with .visible = false
and .RepeatSection = True) I notice that as I go through the sections
making some visible and some invisible, the report only sometimes hangs. Is
that predictable in any way?

In my experience, a repeated group header will hang every
time you do anything that prevents it from printing.

There might(?) be some workarounds using CanShrink,
MoveLayout or ???, depending on what you're trying to
accomplish.

 

[david epsom dot com dot au]

Well, the first thing I noticed was that only the 'outermost'
group header was causing a problem. The second thing I noticed
was, that it wasn't that simple....

I've found 'PrintSection' instead of .visible. Reviewing the
comments and code, it looks like RepeatSection was another one
of those poorly implemented enhancements to Access :~(

(david)

 

[Marshall Barton]

Well, the first thing I noticed was that only the 'outermost'
group header was causing a problem. The second thing I noticed
was, that it wasn't that simple....

I've found 'PrintSection' instead of .visible. Reviewing the
comments and code, it looks like RepeatSection was another one
of those poorly implemented enhancements to Access :~(

Yeah, this is definitely a hole in the implementation.

It's been a while since I played around with this issue, but
I think you can set each header control to Null so CanShrink
pulls the section up to (almost?) nothing. Alternatively, I
seem to remember setting the sections MoveLayout False.
effectively using no space.

Did you say that PrintSection = False also works? I don't
remember that being any different than Visible = False, but
my memory is kinda vague (about a lot of things, not just
this issue ;-)

If you get something to work David, be sure to post back
with how you did it.
--
Marsh
MVP [MS Access]

 

[david epsom dot com dot au]

Well it seems to be working now: in the format event of
every header I test my condition and set PrintSection
to false if required. PrintSection is reset to true
for every section, so it needs to be repeatedly set to
false. I don't know if I should be checking the format
count, but at present I'm not:

If InStr(fsHideline, "Hide_0") Then PrintSection = False

It does also avoid the bother of figuring out section
numbers to use in .section(i).visible = false


(david)

Well, the first thing I noticed was that only the 'outermost'
group header was causing a problem. The second thing I noticed
was, that it wasn't that simple....

I've found 'PrintSection' instead of .visible. Reviewing the
comments and code, it looks like RepeatSection was another one
of those poorly implemented enhancements to Access :~(

Yeah, this is definitely a hole in the implementation.

It's been a while since I played around with this issue, but
I think you can set each header control to Null so CanShrink
pulls the section up to (almost?) nothing. Alternatively, I
seem to remember setting the sections MoveLayout False.
effectively using no space.

Did you say that PrintSection = False also works? I don't
remember that being any different than Visible = False, but
my memory is kinda vague (about a lot of things, not just
this issue ;-)

If you get something to work David, be sure to post back
with how you did it.
--
Marsh
MVP [MS Access]

hangs.
Is

 

[Marshall Barton]

That's good to know, David. Thanks for working that out for
the rest of us.