Fence Diagrams

Question

I am attempting to create a Fence Diagram in gINT following directions by Kathleen Holcomb from 2014. These directions may be dated for the version of gINT I am running (gINTCL). 
 After drafting the borings, I go through the steps as listed by Ms. Holcomb. I select two borings from the "Boring Designation" line and click the "preview" icon at the top. I then receive a pop-up window that is titled "Unable to output.". Below this, it reads "Specified Points returned no data. The following Points had no depth-related data: my boring #'s. (After Pass 1)" 
 I unable to understand what this error message means or how to correct it. If someone could direct me, I would be greatly appreciated. 
 
 Dave Hewitt, PG

Kirk Johnson · Answer

The message means that the there is not enough data input that have a corresponding match to the entities that are on the fence report. you would need at least one record with depth related info matching the report. A fence requires North, East , and elevation to be filled out along with 1 Depth related record (IE lithology depth and graphic). I would open your fence diagram in report design and double click on the graphic entity make sure the TABLE.Field represented in the expression matches the table and field contained in the database you are outputting from. For example if your table name is lithology and your field id graphic it would be <> Here is good reference material in the Fence Tutorial. Fence Report Design, Surfaces and Modeling Product(s): gINT Logs, gINT Professional, gINT Professional Plus Version(s): N\A Environment: N\A Area: Report-Fence Subarea: N\A … Last edited 10 months ago in OpenGround | gINT | Keynetix > gINT | Keynetix Wiki

Kirk Johnson · Answer

Hi David, 
 
 Thank you for sending the files. The field names referenced in the report do not match the fields in input. In the project you have fields named Length that represent bottom and a field named Classification for the Graphic. The report would need to match the table.field referenced in the database