Hi,
I have a report design (log) where I want to show the entire depth of the hole on one page, there are multiple holes with varying depths that will use this design.
Currently to do this, I went to LOG REPORT PROPERTIES>Report Structure>Depth Units Page 1 and left it blank.
This fits it all on one page but I have text under the last boundary line that shows up in some white space near the bottom of the page (TEXT VS DEPTH PROPERTIES>Boundary Text>Text Below Last Line) and then some general comments (TEXT VS DEPTH PROPERTIES>Main>Text Expression) that are being split and some of it pushed to a second page. The general comments has the Depth Expression set to the hole depth.
Is there a way to make the white space at the bottom larger to fit both sections of text? Or how do I control the position of the last boundary line?
I have included a screen shot that shows the white space (at the bottom) where the text needs to go.
Thanks.
I realize that the original post is 6 years old, and the OP probably has moved on, but here is a qualified solution in case others are interested or have similar problems.
If the text is entered into the field as a series of lines using carriage returns as it appears in the example provided by the original poster, then the data is essentially a delimited list and the number of lines entered can be found using something similar to <<ListCount(<<Project.Comments>>,"<<cr>>")>>. The depth per page required to fit the entire log plus comments on one page can then be calculated using the formula:
DP = HB x DH/(HB-HT)
where:
DP is the depth per page to set in report properties
HB is the height of the body in the report in inches
DH is the maximum depth of the hole
HT is the total height of the text to be displayed below the bottom of the hole which will be the number of lines of text times the line spacing of the text (in inches). Note that if no line spacing is set in the wrap tab of the entity then gINT assumes 1.5 x the font height. In your case the total number of lines will 1 + 1 + No of lines in general comments (returned by the list count function). One line for text below last boundary line, plus one line that appears to be a blank carraige return, plus the general comments.
Qualifications:
This solution assumes that each line of text in the general comments is short enough so that it does not wrap to a second line.
This solution assumes that the bottom boundary line is not pushed down by lengthy descriptions or thin layers above the end of the boring.
It would probably be wise to round DP up to the next whole number.
You may want to add a little fudge factor into the calculation, so it is not right at the bottom of the page.
I have not tested this solution. If anyone is interested in implementing something similar I can test it.
In the Report Design, click on the icon Log Properties, that looks like a hand holding a paper
How do I get to Log Report Properties?
Yes, the solution above will involve trial and error. gINT does not have a function that will count the number of lines of text you entered in a column.
Thanks for your response.
So if I am understanding it right, this way you would have to trial and error hole by hole the value of additional depth to show beyond the end of the hole to fit the comments at the end.
I was hoping there would be a way using functions to determine how much additional depth after the end of the hole is required to hit the comments.
I imagined it as each additional line of text would correspond to a fixed height on the page, this would be translated into a factor that is multiplied to the depth of the hole to fit. eg: it counts X lines of text in the comments and sets the depth to show as 1.Y multiplied by the hole depth, I imagine the relation between X and Y could be determined based on how tall a line of text is on 1 page.