Results 1 to 9 of 9
  1. #1
    New Lounger
    Join Date
    Nov 2002
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Fields overprint in a Report (2000/2003)

    I've run into a problem with a report (actually a series of reports) that I haven't been able to solve or find posted previously (perhaps I'm using the wrong search terms). In this report there is a text box bound to a memo field that can grow and shrink in a section that can also grow and shrink. Beneath this text box is another similar text box bound to a text field. Sometimes the memo field grows correctly, but other times the memo field expands and prints correctly, but the field underneath isn't pushed down. Instead it prints on top of (overprints) the memo field making an unreadable mess. This problem has occurred in both Access 2000 and 2003 (with databases in both 2000 and 2003 format). The error is very consistent in that the same records always cause the problem, but it doesn't happen for all records. I haven't been able to figure out how records that cause the problem are different from those that don't.

    Has anyone seen this problem before? Any suggestions?

    Thanks.

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Fields overprint in a Report (2000/2003)

    Could you post a stripped down version of the database?
    <UL><LI>Make a copy of the database and work with that.
    <LI>Remove all database objects (tables, queries, forms, reports, macros and modules) that are not relevant to the problem.
    <LI>In the remaining table(s), remove most records - leave only the minimum number necessary to demonstrate the problem.
    <LI>Remove or modify data of a confidential nature.
    <LI>Do a compact and repair (Tools/Database Utilities).
    <LI>Make a zip file containing the database; it should be below 100KB.
    <LI>If you have difficulties getting the zip file below 100 KB, save the database in Access 97 format and then zip it.
    <LI>Attach the zip file to a reply.[/list]That will enable Loungers to look at the problem directly.

  3. #3
    New Lounger
    Join Date
    Nov 2002
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Fields overprint in a Report (2000/2003)

    Sure. Here is a very small version that shows two examples of the problem. Look at the one report in the database. Thanks.
    Attached Files Attached Files

  4. #4
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Fields overprint in a Report (2000/2003)

    From one Bell to another: <img src=/S/grin.gif border=0 alt=grin width=15 height=15>
    That is indeed a strange one - however if I change the Group Comments text box to a zero height, turn of the can shrink and then do a print preview it seems to be OK. At least the second and third page display OK, though I appear to be getting a blank line after Group comments. Another issue here appears to be that you are using some form of either hard returns or line feeds or something in the data, and I suspect that is contributing to the problem. Try taking them out and see what happens when you simply put spaces. FYI, you can insert a Carriage Return and LineFeed by holding down CTRL and pressing ENTER in Access. Hope this helps.
    Wendell

  5. #5
    New Lounger
    Join Date
    Nov 2002
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Fields overprint in a Report (2000/2003)

    The problem is not with the hard carriage returns. Although this short example has hard carriage returns, there are other instances where this happens that don't have them. I should also point out that if I remove the iif condition and just print the memo field the problem also happens.

    I don't understand what you mean by setting the height to zero and turning off can shrink and can grow. When I do that the group comments to not print at all? If they're not there, then they don't overlap, but I really need to see them.

    Thanks for your help.

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Fields overprint in a Report (2000/2003)

    Sorry I wasn't more clear - turn off only the can shrink - if the height is set to zero, it can't shrink anyhow. (I looked at the IIF statement and tried getting rid of it too, and as you note it still behaves the same.)
    Wendell

  7. #7
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Fields overprint in a Report (2000/2003)

    There is a very slight vertical overlap between controls in the Grp_Number group header. This prevents Can Grow from functioning properly. It is very important to ensure that there is NO vertical overlap between controls if you use Can Grow / Can Shrink. In this case, setting the height of all controls in the group header to .4 cm (.16 inch) is sufficient to correct it.

  8. #8
    New Lounger
    Join Date
    Nov 2002
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Fields overprint in a Report (2000/2003)

    Sorry, I misread your earlier post. When I try it, it does work as you desribe. When I move the lower fields up so they touch the now zero height group comments box, the problem recurs. If I move them down ever so slightly (turning off snap to grid), then the report prints correctly with just a minimum of extra space. I can live with that. I guess there is something about touching or overlapping controls that must be related to the problem.

    Thanks again for your help.

  9. #9
    New Lounger
    Join Date
    Nov 2002
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Fields overprint in a Report (2000/2003)

    Many thanks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •