![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have ans Access 2010 SP1 report with a field "BoatName" set to CanGrow and CanShrink both set to True as is the Report's Detail Section. The field is not that very wide (1.649cm), and uses Arial 7 font. AS far as I can see the 600 or so records all print perfectly with the exception of a boat called "Mad Scramble" which only prints out as "Mad" If I change the name od the boat to "Mad Scramble" (2 spaces between the words) all is OK. I have retyped the boat name in case there was a hidden illegal field or a carriage return or line feed. Definately think this is a bug. Anyone else had anything similar? Phil |
#3
| |||
| |||
|
|
On Jan 15, 8:46*am, "Phil" <p... (AT) stantonfamily (DOT) co.uk> wrote: I have ans Access 2010 SP1 report with a field "BoatName" set to CanGrow and CanShrink both set to True as is the Report's Detail Section. The field i s not that very wide (1.649cm), and uses Arial 7 font. AS far as I can see the 600 or so records all print perfectly with the exception of a boat called "Mad Scramble" which only prints out as "Mad" If I change the name od the boat to "Mad Scramble" (2 spaces between the words) all is OK. I have ret yped the boat name in case there was a hidden illegal field or a carriage retu rn or line feed. Definately think this is a bug. Anyone else had anything similar? Phil You could make the control source a function. You pass the boat name to the function and return the boat name. Then run a test and do a debug.print if the left(boatname,3) is Mad the asciii values of each character. |
#4
| |||
| |||
|
|
On 15/01/2012 18:25:03, Patrick Finucane wrote: On Jan 15, 8:46 am, "Phil"<p... (AT) stantonfamily (DOT) co.uk> wrote: I have ans Access 2010 SP1 report with a field "BoatName" set to CanGrow and CanShrink both set to True as is the Report's Detail Section. The field i s not that very wide (1.649cm), and uses Arial 7 font. AS far as I can see the 600 or so records all print perfectly with the exception of a boat called "Mad Scramble" which only prints out as "Mad" If I change the name od the boat to "Mad Scramble" (2 spaces between the words) all is OK. I have ret yped the boat name in case there was a hidden illegal field or a carriage retu rn or line feed. Definately think this is a bug. Anyone else had anything similar? Phil You could make the control source a function. You pass the boat name to the function and return the boat name. Then run a test and do a debug.print if the left(boatname,3) is Mad the asciii values of each character. No Go, Patrick All Ascii codes OK I should have mentioned that "Mad Scramble" with 2 spaces prints out correctly on 2 lines. Phil |
#5
| |||
| |||
|
|
On 2012-01-15 9:28 PM, Phil wrote: On 15/01/2012 18:25:03, Patrick Finucane wrote: On Jan 15, 8:46 am, "Phil"<p... (AT) stantonfamily (DOT) co.uk> wrote: I have ans Access 2010 SP1 report with a field "BoatName" set to CanGrow and CanShrink both set to True as is the Report's Detail Section. The field i s not that very wide (1.649cm), and uses Arial 7 font. AS far as I can see the 600 or so records all print perfectly with the exception of a boat called "Mad Scramble" which only prints out as "Mad" If I change the name od the boat to "Mad Scramble" (2 spaces between the words) all is OK. I have ret yped the boat name in case there was a hidden illegal field or a carriage retu rn or line feed. Definately think this is a bug. Anyone else had anything similar? Phil You could make the control source a function. You pass the boat name to the function and return the boat name. Then run a test and do a debug.print if the left(boatname,3) is Mad the asciii values of each character. No Go, Patrick All Ascii codes OK I should have mentioned that "Mad Scramble" with 2 spaces prints out correctly on 2 lines. Phil Phil, Sounds like it's working as designed and I don't think there is any problem with your data. 'CanShrink' and 'CanGrow' only apply to the vertical size and setting them to True results in the field's height (not width !) being automatically increased to accommodate as many lines as are necessary to display all the data. This is why 'Mad Scramble' wraps across two lines; if you set the CanGrow flag to 'False' you will probably only see 'Mad', because that's all the text that will fit in the field you've designed (which I presume to be only one line high). The reason that CanShrink/Grow only apply to the field's Height and not its Width is that the latter would cause undesirable behaviour. Vertical growth only pushes fields down, causing the report to be longer (more pages), whereas horizontal growth would push fields of the right edge of the paper. It doesn't matter when a report becomes 50 pages long, but it does matter when a report becomes 50 pages wide. HTH, Jan |
![]() |
| Thread Tools | |
| Display Modes | |
| |