By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,687 Members | 2,065 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,687 IT Pros & Developers. It's quick & easy.

Report CAN GROW problem with Memo field

P: n/a
Mal
I have an ACC 2000 database that has a strange behaviour

I have a small table, with just a few fields...

My report has very simple grouping and sorting, no code bar a NODATA
event.

I have a memo field
When CAN GROW is set to NO everything works just fine.
When CAN GROW is set to YES - watch out.... One record causes BIG
problems.
It generates endless pages of the header but no data for the record.

I have discovered that the problem occurs when the CAN GROW property
would cause the field to grow beyond the page size.

When I shrink the text size then everything works just fine.

Is there a good workaround to this problem behaviour, or should I
approach this in a different manner.

Thanks,
Mal.
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Have you applied all three Service Packs/Releases for Access 2000 and all
the additional fixes from Office Update? (Just as a matter of interest for
fans of Access 2000, this "Work of Art" has just gone out of "mainstream
maintenance" as of June 30. Check the Microsoft web site for maintenance
schedules and definitions. I am not sure what this maintenance status may
mean if this is a newly-discovered/reported product defect -- whether it
might still be corrected or if upgrading to a later version would be the
answer.)

In a quick check, I did not find a Knowledge Base article specific to Access
2000 on this subject.

Where in the report is the offending text box located? And, how long is the
memo field in the record causing the problem? I'm not quite sure what you
mean "shrink the text size everything works just fine" -- does that mean
"limit the number of characters" or "use a smaller font" or something else?
Please clarify and perhaps someone can be of help.

Larry Linson
Microsoft Access MVP

"Mal" <ma******@hotmail.com> wrote in message
news:75**************************@posting.google.c om...
I have an ACC 2000 database that has a strange behaviour

I have a small table, with just a few fields...

My report has very simple grouping and sorting, no code bar a NODATA
event.

I have a memo field
When CAN GROW is set to NO everything works just fine.
When CAN GROW is set to YES - watch out.... One record causes BIG
problems.
It generates endless pages of the header but no data for the record.

I have discovered that the problem occurs when the CAN GROW property
would cause the field to grow beyond the page size.

When I shrink the text size then everything works just fine.

Is there a good workaround to this problem behaviour, or should I
approach this in a different manner.

Thanks,
Mal.

Nov 13 '05 #2

P: n/a
Larry,

My first impression was that I had a bad record or something...but no.
The memo field is in the detail of the report (2 levels of grouping above
that)
both it and the detail section are set to Can Grow = yes

The problem isn't even the amount of data....the particular record initially
had a LEN of 5455
The only change I made was to reduce the font size (to 6)...and things
worked fine.

I then increased the amount of data in the record...and eventually caused
the same error..

I went back to the original record....font size 12 and got the error.
Reduced the data in this memo field until it would work...which was once it
was contained on a single page.

Just for kicks I then went back to the original record again, stripped down
my page margins to 0.1, and left the font size at 12. Now I only had to
strip off less data until it would once again contain itself to a single
page.

For a few more kicks I tried to recreate the problem in Acc 97 here at
home....can't do it...The field expands over several pages with no
problem....

Any ideas? Should I feel some strange sense of pride in discovering an as
yet documented (KB article) for Access????.

Mal.
"Larry Linson" <bo*****@localhost.not> wrote in message
news:jn*******************@nwrddc03.gnilink.net...
Have you applied all three Service Packs/Releases for Access 2000 and all
the additional fixes from Office Update? (Just as a matter of interest for
fans of Access 2000, this "Work of Art" has just gone out of "mainstream
maintenance" as of June 30. Check the Microsoft web site for maintenance
schedules and definitions. I am not sure what this maintenance status may
mean if this is a newly-discovered/reported product defect -- whether it
might still be corrected or if upgrading to a later version would be the
answer.)

In a quick check, I did not find a Knowledge Base article specific to Access 2000 on this subject.

Where in the report is the offending text box located? And, how long is the memo field in the record causing the problem? I'm not quite sure what you
mean "shrink the text size everything works just fine" -- does that mean
"limit the number of characters" or "use a smaller font" or something else? Please clarify and perhaps someone can be of help.

Larry Linson
Microsoft Access MVP

"Mal" <ma******@hotmail.com> wrote in message
news:75**************************@posting.google.c om...
I have an ACC 2000 database that has a strange behaviour

I have a small table, with just a few fields...

My report has very simple grouping and sorting, no code bar a NODATA
event.

I have a memo field
When CAN GROW is set to NO everything works just fine.
When CAN GROW is set to YES - watch out.... One record causes BIG
problems.
It generates endless pages of the header but no data for the record.

I have discovered that the problem occurs when the CAN GROW property
would cause the field to grow beyond the page size.

When I shrink the text size then everything works just fine.

Is there a good workaround to this problem behaviour, or should I
approach this in a different manner.

Thanks,
Mal.


Nov 13 '05 #3

P: n/a
Because Access 2000 had so many unresolved issues for so long, I don't have
it installed on this machine, and the old machine where I could bring it up
has not been updated "since I don't know when".

All I can suggest is to check and make certain that you have all three
Service Packs / Service Releases for Access 2000 and all the later updates
via the Office Update option in Windows Update.

Because it is out of mainstream support, now, I don't even know if it will
do any good to report it to Microsoft Tech Support. I can get a one-page
skip with Access 2002, with some similar data, if I specify KeepTogether =
Yes for the Detail Section. But if I change KeepTogether to No for the
Detail Section, the TextBox containing a 6000-character Memo begins
immediately after the other Detail Section data.

I suspect you've tried most combinations. Do you get the same effect if your
Detail Section's KeepTogether is set to No?

Larry Linson
Microsoft Access MVP
"Mal Reeve" <lo*****@earthlink.net> wrote in message
news:JQ******************@newsread2.news.atl.earth link.net...
Larry,

My first impression was that I had a bad record or something...but no.
The memo field is in the detail of the report (2 levels of grouping above
that)
both it and the detail section are set to Can Grow = yes

The problem isn't even the amount of data....the particular record initially had a LEN of 5455
The only change I made was to reduce the font size (to 6)...and things
worked fine.

I then increased the amount of data in the record...and eventually caused
the same error..

I went back to the original record....font size 12 and got the error.
Reduced the data in this memo field until it would work...which was once it was contained on a single page.

Just for kicks I then went back to the original record again, stripped down my page margins to 0.1, and left the font size at 12. Now I only had to
strip off less data until it would once again contain itself to a single
page.

For a few more kicks I tried to recreate the problem in Acc 97 here at
home....can't do it...The field expands over several pages with no
problem....

Any ideas? Should I feel some strange sense of pride in discovering an as
yet documented (KB article) for Access????.

Mal.
"Larry Linson" <bo*****@localhost.not> wrote in message
news:jn*******************@nwrddc03.gnilink.net...
Have you applied all three Service Packs/Releases for Access 2000 and all the additional fixes from Office Update? (Just as a matter of interest for fans of Access 2000, this "Work of Art" has just gone out of "mainstream
maintenance" as of June 30. Check the Microsoft web site for maintenance
schedules and definitions. I am not sure what this maintenance status may mean if this is a newly-discovered/reported product defect -- whether it
might still be corrected or if upgrading to a later version would be the
answer.)

In a quick check, I did not find a Knowledge Base article specific to

Access
2000 on this subject.

Where in the report is the offending text box located? And, how long is

the
memo field in the record causing the problem? I'm not quite sure what you mean "shrink the text size everything works just fine" -- does that mean
"limit the number of characters" or "use a smaller font" or something

else?
Please clarify and perhaps someone can be of help.

Larry Linson
Microsoft Access MVP

"Mal" <ma******@hotmail.com> wrote in message
news:75**************************@posting.google.c om...
I have an ACC 2000 database that has a strange behaviour

I have a small table, with just a few fields...

My report has very simple grouping and sorting, no code bar a NODATA
event.

I have a memo field
When CAN GROW is set to NO everything works just fine.
When CAN GROW is set to YES - watch out.... One record causes BIG
problems.
It generates endless pages of the header but no data for the record.

I have discovered that the problem occurs when the CAN GROW property
would cause the field to grow beyond the page size.

When I shrink the text size then everything works just fine.

Is there a good workaround to this problem behaviour, or should I
approach this in a different manner.

Thanks,
Mal.



Nov 13 '05 #4

P: n/a
Mal
"Larry Linson" <bo*****@localhost.not> wrote in message news:<iV*******************@nwrddc01.gnilink.net>. ..
Because Access 2000 had so many unresolved issues for so long, I don't have
it installed on this machine, and the old machine where I could bring it up
has not been updated "since I don't know when".

All I can suggest is to check and make certain that you have all three
Service Packs / Service Releases for Access 2000 and all the later updates
via the Office Update option in Windows Update.

Because it is out of mainstream support, now, I don't even know if it will
do any good to report it to Microsoft Tech Support. I can get a one-page
skip with Access 2002, with some similar data, if I specify KeepTogether =
Yes for the Detail Section. But if I change KeepTogether to No for the
Detail Section, the TextBox containing a 6000-character Memo begins
immediately after the other Detail Section data.

I suspect you've tried most combinations. Do you get the same effect if your
Detail Section's KeepTogether is set to No?

Larry Linson
Microsoft Access MVP
"Mal Reeve" <lo*****@earthlink.net> wrote in message
news:JQ******************@newsread2.news.atl.earth link.net...
Larry,

My first impression was that I had a bad record or something...but no.
The memo field is in the detail of the report (2 levels of grouping above
that)
both it and the detail section are set to Can Grow = yes

The problem isn't even the amount of data....the particular record

initially
had a LEN of 5455
The only change I made was to reduce the font size (to 6)...and things
worked fine.

I then increased the amount of data in the record...and eventually caused
the same error..

I went back to the original record....font size 12 and got the error.
Reduced the data in this memo field until it would work...which was once

it
was contained on a single page.

Just for kicks I then went back to the original record again, stripped

down
my page margins to 0.1, and left the font size at 12. Now I only had to
strip off less data until it would once again contain itself to a single
page.

For a few more kicks I tried to recreate the problem in Acc 97 here at
home....can't do it...The field expands over several pages with no
problem....

Any ideas? Should I feel some strange sense of pride in discovering an as
yet documented (KB article) for Access????.

Mal.
"Larry Linson" <bo*****@localhost.not> wrote in message
news:jn*******************@nwrddc03.gnilink.net...
Have you applied all three Service Packs/Releases for Access 2000 and all the additional fixes from Office Update? (Just as a matter of interest for fans of Access 2000, this "Work of Art" has just gone out of "mainstream
maintenance" as of June 30. Check the Microsoft web site for maintenance
schedules and definitions. I am not sure what this maintenance status may mean if this is a newly-discovered/reported product defect -- whether it
might still be corrected or if upgrading to a later version would be the
answer.)

In a quick check, I did not find a Knowledge Base article specific to Access 2000 on this subject.

Where in the report is the offending text box located? And, how long is the memo field in the record causing the problem? I'm not quite sure what you mean "shrink the text size everything works just fine" -- does that mean
"limit the number of characters" or "use a smaller font" or something else? Please clarify and perhaps someone can be of help.

Larry Linson
Microsoft Access MVP

"Mal" <ma******@hotmail.com> wrote in message
news:75**************************@posting.google.c om...
> I have an ACC 2000 database that has a strange behaviour
>
> I have a small table, with just a few fields...
>
> My report has very simple grouping and sorting, no code bar a NODATA
> event.
>
> I have a memo field
> When CAN GROW is set to NO everything works just fine.
> When CAN GROW is set to YES - watch out.... One record causes BIG
> problems.
> It generates endless pages of the header but no data for the record.
>
> I have discovered that the problem occurs when the CAN GROW property
> would cause the field to grow beyond the page size.
>
> When I shrink the text size then everything works just fine.
>
> Is there a good workaround to this problem behaviour, or should I
> approach this in a different manner.
>
> Thanks,
> Mal.



Larry,

Thanks for the advice...
Tried all the different combinations ( i think) with no sucess.
Looking at a rollback or upgrade of Access instead.

Mal.
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.