How to Add Remarks to Report Design.

Hi there, 

I'd like to organize some notes at the end of the borehole logs. 

Currently I write the notes in the "Notes" section of the Borehole Input Section but they do not format neatly with each note on a new line. 

When I add some input information in the Remark Input tab, they do not show up on the template. 

I think I first need to add the remarks to the template design. How do I do this? 

Thanks so much

Ismena 

  • Hi Ismena,

    There are few different ways. Since this looks like information you are showing at the end of borehole you could add it to the boundary text expression. To modify it ..open report design . open the material description column . goto boundary text and modify the text below last line expression. Either add your own table and field or modify the User system data expression in Data Design ..User system data.

    The Notes field in the standard dataset is just a text field for a short note. It is usually referenced in the header of the report. The remarks table is a depth table where you are recording downhole remarks at depth. 

    If you created a new memo field in the point table you could do that also (this allows carriage returns) . And then reference that in your boundary text expression.

    Here are some links to other users who have done other things for end of hole notes

    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…
    By in OpenGround | gINT | Keynetix > gINT Forum

    Also see report design tutorial.

    Access gINT Tutorials: Tutorials Getting To Know gINT Tutorial Performing Data Entry Tutorial Using Data Design Tutorial Logs Tutorial for Log Report Design Advanced…
    Last edited in OpenGround | gINT | Keynetix > gINT | Keynetix Wiki

    If any of these don't look like a good fit, there are other ways. Just file a quick service request and we can call you back and walk you through a variety of options.

    Access Service Request Manager as described here . Below describes how to log a new technical, product-related Service Request using Technical Support tile; other categories/forms follow the same design…

  • If you merely want multiple notes entered into a single field to start on a new line you can simply embed a gINT carriage return code in the text.  This should work regardless of whether the field is a text field or a memo field.  For example, the text

    This is a note<<cr>>this is a second note

    will print as

    This is a note

    this is a second note

    The note would still wrap based on the length of each line and the settings in the entity that prints it but the formatting code forces a new line to start. This works with other formatting codes as well such as bold <<b>> underline <<u>> etc. I am not a proponent of including gINT formatting codes in data as it makes the data less portable but this is one way to solve your stated concern.  

    If your note is assembled from several different fields, the carriage returns can be included in the expression used to assemble the note. for example:

    The expression <<ListBuildSepTrim("<<cr>>",<<table1.field1>>,<<table1.field2>>,<<table1.field3>>)>>

    Will assemble the notes in field1, field2, and field3 into a single note with each note beginning on a new line.

  • Hi Kirk .

    I finally got around to trying your solution. I like the idea of editing the report template, but the values change for each well and I could not figure out how to call certain values from elsewhere in the database.  I think I will resolve by adding a false lithology entry after the well depth. 

  • HI szang, 

    I am not sure what a gint carriage return code is but I did try using formatting in the remarks section - hence the bolded in my example. The <<N>> entry did not create a new line so I don't think this solves my original concern. 

  • Ismena, the code for carriage return is <<cr>>, that will create a new line (see Szang's example)