I'm convinced this is an Access 2010 shortcoming but I haven't been able to find it reported anywhere on the interenets....
What I have is an Access report that is extremely large. It is not developed like a normalized report in that it doesn't utilize the detail section of the report, instead if has 5 grouping headers all bound to a recordsource which has an extremely large number of fields, so many that I can't add anymore to the query.
The report is used to display a checklist report which is filled out by a form that has subforms and tab controls where field count isn't an issue.
The checklist consists of dozens and dozens of questions which consist of a label on the left, a ['Yes', 'No', 'N/A'] option group frame in the middle, then a textbox to the right of that for comments with the 'can grow' option set true.
In order to ensure the horizontal lines are pushed down when the comments grow, we've used the textbox's border, stretched it completely across the report and set the textbox's left margin to 4.55".
The issue is when there is enough text to make the field grow, it causes the field to grow much much larger then just one line. This worked fine in Access 2003 and Access 2007 but now users who only have Access 2010 can't print out the report without issues.
To reproduce the issue. Create a new report, set the page properties to Landscape, Narrow Margins .25 all the way around. Stretch the page width to 10.5 to take up the whole page. Add a text box that starts at left 0 with a width of 10.5. Set the text box left margin to 4.55". Set the controlsource of the text box to random text but long enough to span more than 1 line, something like (="hey this is some long text that I'm just using to make sure the report will bump the text onto the next line.....Microsoft is so aggrevating."). make sure you have the border style of the textbox to solid so you can see that it grew un-necessarily large.
Print Preview the report and you'll get exactly what it shown in the snapshot attached.
i'm stumped, anyone have any ideas?
We've already entertained putting data in subreports but then sometimes data is cut off because the parent report doesn't know where questions start and questions finished since it's all one huge 1 record report.
What I have is an Access report that is extremely large. It is not developed like a normalized report in that it doesn't utilize the detail section of the report, instead if has 5 grouping headers all bound to a recordsource which has an extremely large number of fields, so many that I can't add anymore to the query.
The report is used to display a checklist report which is filled out by a form that has subforms and tab controls where field count isn't an issue.
The checklist consists of dozens and dozens of questions which consist of a label on the left, a ['Yes', 'No', 'N/A'] option group frame in the middle, then a textbox to the right of that for comments with the 'can grow' option set true.
In order to ensure the horizontal lines are pushed down when the comments grow, we've used the textbox's border, stretched it completely across the report and set the textbox's left margin to 4.55".
The issue is when there is enough text to make the field grow, it causes the field to grow much much larger then just one line. This worked fine in Access 2003 and Access 2007 but now users who only have Access 2010 can't print out the report without issues.
To reproduce the issue. Create a new report, set the page properties to Landscape, Narrow Margins .25 all the way around. Stretch the page width to 10.5 to take up the whole page. Add a text box that starts at left 0 with a width of 10.5. Set the text box left margin to 4.55". Set the controlsource of the text box to random text but long enough to span more than 1 line, something like (="hey this is some long text that I'm just using to make sure the report will bump the text onto the next line.....Microsoft is so aggrevating."). make sure you have the border style of the textbox to solid so you can see that it grew un-necessarily large.
Print Preview the report and you'll get exactly what it shown in the snapshot attached.
i'm stumped, anyone have any ideas?
We've already entertained putting data in subreports but then sometimes data is cut off because the parent report doesn't know where questions start and questions finished since it's all one huge 1 record report.
