Hello,
I currently have two tables with the following key sets:
MONP - PointID,DepthMONR - PointID,Depth,DateTime (with the Parent Table of MONP)
I would like to have a third table MONZ with MONR as the parent table.To do this the only Key Set I can select to make this possible is "PoinID,Depth,DateTime". All other key sets do not allow me to select MONR ast the parent table.
However, when select "PoinID,Depth,DateTime" as the key set it inserts and extra datetime field as a required key in my MONZ table i.e:PointIDDepthMONP_IDMONR_DateTimeDateTime <--This is the extra field it inserts
I would like the MONZ table structure to be as follows (required keys indicated with *):PointID* Depth* MONP_ID* MONR_DateTime*MONZ_Depth*MONZ_Reading
I suspect that I need the following key set PoinID,Depth,DateTime,ItemKey but this is not in the list.
Can someone please direct me to how I can achieve the desired MONZ table structure.
Thanks.
Calan.
Calan, the table names you give indicate that this may be an AGS structure gINT project. I have emailed you some additional information, but generally speaking, if you need a gINT project to be able to export into or import from AGS files, you will not be able to add tables or modify existing tables in the gINT AGS structure at will.
For non-AGS gINT projects, it is possible to build a child table with the keysets you want by modifying the parent tables. The top parent table needs to be a child of POINT, with a [PointID, Depth] keyset. Add a Date/Time field (don't call it DateTime, which is a reserved word for this purpose - as an example, call it Date), Click on the box to Allow duplicate Depth values for a Point record, and save the change to the table. Then in the Properties for this table, add the Date field to the property Additional Key Fields.
Now when you create the child table with a [PointID, Depth, Reading] keyset, this parent table will be in the list of possible parents (because the Date field is an additional key), and you will have PointID, Depth and Date included automatically from the parent. Reading fields are Double precision type, and this Reading field can be captioned as "Depth". Be sure to name the child Reading field (MONZ_Reading) something besides "Reading".
Thankyou Pat,
You are correct, I was trying to preserved an AGS structure as much as possible while still being able to include additional tables to suit our needs. Your suggestion of not using the reserved "DateTime" name is very helpful, I need to decided now how much I conform to the AGS structure and how much I rely on transformation files.
I have also replyed to you email.
Much appreciated.
Calan,
MONP/MONR is not a good working structure, it is a reasonable data interchange structure. To make a working database, dispose of MONP/MONR and create tables for each instrument that model how the data is collected. Then change the AGS gci/gcx files to suit. Don't let a data interchange standard restrict you, just ensure you capture the granularity of data required by the data interchange standard.
Phil WadeDatgelBentley Channel Partner and Developer PartnerE: phil.wade@datgel.com | T: +61 2 8202 8600 & +65 6631 9780
Get the most out of gINT with Datgel Tools.