Trouble importing lithology with points/soil borings

I am very new to gINT and am in the process of converting soil borings from an .mdb file to be able to bring into ORD. I was able to successfully import my points by creating a correspondence file, which I started with the sample/default table. But when I try to add the lithology to the points it does not work? I can't seem to find information on how the lithology table works, am I not supposed to use the same point name as the "Point" table? 

I attached my excel sheet that I am trying to import but it won't seem to let me add my correspondence file (.gci)

This is the document that I am using and has been helpful. 

https://communities.bentley.com/products/geotechnical1/w/wiki/12398/using-correspondence-files-for-importing-and-exporting

TEST-CORR-2.xls

  • Without knowing what your data structure looks like (there are many samples available), what your correspondence file looks like, or what is displayed in the import log window after your import runs, it is difficult to make specific suggestions. However the following are some general tips to make importing data easier.

    1. To answer your question, the lithology table it is typically set up as a child of the point table and is linked to the point table through the key field PointID. When you import data, the parent table must be imported first otherwise the lithology table will not have anything to link to. The PointID in the lithology table  must match exactly to the PointID in the point table.

    2. When creating correspondence files, it is best to use the correspondence file tool in gINT. Set the source file to your excel file and the target file to the data structure (.gdt) file you are using. For each table you want to import into, select the default sheet in your excel file using the pull down. Then use the field name pasting tool to create the correspondence between source and target. Using the field pasting tool eliminates errors due to misspelled field and sheet names and errors due to improper syntax (missing delimiters, missing or wrong punctuation etc )

    3. When creating the correspondence for the lithology table, make sure the source  for the PointID field points to the corresponding table in your excel file (in your case the GEOL table) and not to the point table.

    4. Some data structures have required fields. If nothing is imported into a required field,  the entire record will be ignored.

    5. Some fields may have restrictions that limit the type of data and the specific entries that are allowed. If your data type does not match or the data does not meet the restrictions, it will be rejected. There are many functions available in the function pasting tool that can help you correct type mismatches or combine multiple source fields into one target field.

    6. The import log that is displayed after you execute an import is very helpful in debugging issues. You can save it to a file before closing the window for future reference. Read it carefully.