Moving end of hole notes to blank page

Hi All,

I have my end of hole notes in a table and have previously referenced them onto my logs in the boundary text using <<User System Data.Termination Note>>. However, now I have a log that doesn't fit my notes onto the last page and therefore need my notes to continue onto a new page. What is the easiest way to accomplish this? I thought this would be relatively easy to accomplish, but I can't seem to get it working. Thanks!

Parents
  • Kirk's solution will work but you will end up with logs that are printed at different scales within one project. No mater what scale you select, there will always be at least one boring that terminates at or near the end of the page and causes the problem. I implemented the following solution that might help you:

    My end of boring text is automatically generated using the boundary line text property in the text vs depth entity.  It will always generate a single line of text so if you are referencing a field that has more than one line of text this may not work for you.


    When the boring is close to the end of the page, this boundary line text will print below the body of the report in the footer area.  Problem is that I print boring notes in the footer area so the boundary line text interferes with it.


    To overcome this, I formatted my boring notes to add a line feed before the notes when the end of the boring is within 0.1" of the end of a page. The formula I use to do this is:

    <<IIf(<<Calc((<<Calc((<<LogPgDepthBot>>-<<Max(<<LITHOLOGY.Bottom>>)>>)/<<LogVS>>)>> < 0.1) _
          And (<<Calc((<<LogPgDepthBot>>-<<Max(<<LITHOLOGY.Bottom>>)>>)/<<LogVS>>)>> >= 0))>>,_
             <<CR>>_
    )>>_
    <<POINT.Notes>>

    This works as follows:
    When I print a log at 20 ft per page the vertical scale is 3'/inch so if the last bottom depth is 19.7' the above equation evaluates as
    (20-19.7)/3 = 0.1"
    0.1" is not less than 0.1 but greater than or equal to 0 so the carriage return is not printed and the notes appear in their normal place. (note the 0.1" criteria is because I am using a font that is 0.08" high in the text vs depth entity)

    When the last bottom depth is 19.8' the equation evaluates as
    (20-19.8)/3 = 0.0666"
    0.066 is between 0 and 0.1 so the carriage return is printed and the notes are bumped down one line. Note however that I lose one available line for the notes and if the notes are long they could extend outside the space allotted for them.

    This works fine but if the description text is long enough to cause the bottom line to bump down a special case exists. In this case the boundary line text is automatically bumped to the next page and another page is generated.  The equation in the notes text doesn't know this and will still bump the notes down one line if the last bottom depth is within 0.1" of the bottom of the page even though it does not need to.

    Examples are shown in the picture below.

  • Another way to approach this would be to use the second text tab of the depth vs text entity.  This will only work if you are not already using the second text tab for some other purpose but if it is available it will automatically accomplish what you desire.  Simply set the depth expression property to <<max(<<lithology.bottom>>)>> or something similar based on your data structure and the column you are printing the end of log notes in.  The text expression property would be <<POINT.Notes>> or whatever expression you use to generate your end of log notes.  Set the override vertical offset property to a negative value to offset the notes the desired distance below the end of the log.

     

    This will force the end of log notes onto another page if there is not enough room for them at the bottom of the last page of the log.  This will work even if your end of log notes are the length of a mini novel and wrap to numerous lines.  It also works if the bottom line of the log is bumped down due to a long description. It does not keep the notes together, ie it will split a multi-line note between two pages if there is enough room at the end of the log for some, but not all, of the end of log note.

Reply
  • Another way to approach this would be to use the second text tab of the depth vs text entity.  This will only work if you are not already using the second text tab for some other purpose but if it is available it will automatically accomplish what you desire.  Simply set the depth expression property to <<max(<<lithology.bottom>>)>> or something similar based on your data structure and the column you are printing the end of log notes in.  The text expression property would be <<POINT.Notes>> or whatever expression you use to generate your end of log notes.  Set the override vertical offset property to a negative value to offset the notes the desired distance below the end of the log.

     

    This will force the end of log notes onto another page if there is not enough room for them at the bottom of the last page of the log.  This will work even if your end of log notes are the length of a mini novel and wrap to numerous lines.  It also works if the bottom line of the log is bumped down due to a long description. It does not keep the notes together, ie it will split a multi-line note between two pages if there is enough room at the end of the log for some, but not all, of the end of log note.

Children
No Data