Graphic Column from fields in two different tables

Question

I've looked around the forum and wikis etc. and can't figure out how to do this for some reason, although it seems simple enough to me. Probably just my lack of understanding the various functions that are available.

I'm trying to make a graphic column (Column - Graphic Column, not an individual body entity Graphic Column) in a log report showing the symbol for the soil/rock type. I have one table for soil component descriptions, and a different table for rock component descriptions. Each table has a Graphic field, i.e. <<SOIL DESCRIPTION.GRAPHIC>> and <<ROCK DESCRIPTION.GRAPHIC>>. Both of these fields use the Graphic!matl lookup list. Each table also has Depth and Bottom fields for the top depth and bottom depth.

How do I get the column to use both of these tables and the appropriate fields in the Top Depth, Bottom Depth, and Fill Type properties? Do I just need to use 2 columns? (Previously our log report used 2 individual body entity graphic columns with the same X value to accomplish this)

Thanks for any help!

SH14277 · Accepted Answer

Hello, I did manage to find a way to get both tables into the same graphic column. I entered the Top Depth Expression as: <> and the Bottom Depth Expression as: <>,<>)>> and entered the Fill Type[!Symbol] as: Matl!<>,<>)>> and it works. I found this solution in an odd place, under the gINT Help entry for Variable Legend Entity Overview, near the end of the entry. Since I was also trying to get a Graphic Text Doc to show all of the material symbols in a single Variable Legend Entity, rather than in two entities (1 for soil and 1 for rock) as they currently are, this was serendipitous. However, now I can't figure out how to get a single variable legend entity to work. I tried entering the above FirstData expression under "Field with Data," but no dice. It's not a big deal I guess, and might be impossible since this is a separate Graphic Text Doc and not on the Log report. Thanks again for your help.

Kathleen Holcomb · Answer

Hello, 
 For your situation, I believe you will need to keep using 2 columns. Otherwise, you would have to write a complex SQL expression. Almost anytime the data is coming from 2 different tables you will run into this problem. 
 By they way, text columns and text vs depth entities do have an option for data coming from different tables, and that is to use the Second Text Spec tab for the second table.