Hi all,
Is there any ideas why the DICT table is not exported in the AGS file?
The table is set in the database (with data as it should) and the gcx file looks ok. It's an AGS4 file export.
Thanks.
Dennis,
The AGS4 file that gets created when you export from a gINT database will only have the DICT Group if your gINT AGS4 database has non-standard AGS Group and AGS Heading names.
What are you using for your AGS4 gINT database? Did you setup the database yourself?
Hi Dave,
Yes I've setup the database myself. I have a DICT table with the appropriate headings and the correspondence file as suppose to, but the DICT table is still not exported.
I'm using a AGS4 database so it would be easier and "straight forward" (as possible as it can be within gINT) to deal AGS4 data transfer files, without creating a massive and complex correspondence file.
Again, there will only be a DICT section in the exported AGS file if you have Groups or Headings in your database that are non-standard.
With AGS3 and gINT there were many fields and some tables in the gINT AGS database there were non-standard, so the DICT section in the exported AGS file could be rather large.
With AGS4 the AGS committee has added many more groups and headings so many in fact that I would be surprised if you still needed to add more. But, it is possible and that is where the DICT section comes into play to indicate what tables and fields are part of your gINT database that are non-standard groups and headings.
Also, because of some design issues with respect to how gINT databases are setup (gINT databases are relational databases) some compromises are necessary in designing a gINT database to work with the AGS4 standard. And, therefore, a Correspondence File is necessary but it shouldn't need to be too complex.
Bentley will eventually be posting an example gINT AGS4 compatible database and a set of import and export Correspondence Files.
The missing DICT section is likely due to what I indicated at the beginning and is probably fine, unless you know of one or more non-standard Groups or Headings in your database structure that should be getting exported.
Dave,
I agree with you and what you say on AGS is common knowlegde. My question is how exactly the DICT table is handled within gINT? How you actually identify the non-standard Groups or Headings? For instance in fact there are some non-standard Headings in my database, how you can actually export them to the AGS4 file?
You define the non-standard groups and headings in the DICT table in your gINT database.
For example, here are some of the fields in the DICT table from a gINT database.
The example data below is actually from an AGS3 database that I imported into an AGS4 database and this group and these headings are now part of the standard AGS4 structure. But, this should give you an idea as to what needs to go into the DICT table in your gINT database.
The gINT program has specific code to deal with the DICT table when exporting data. If there are no groups and/or headings defined in the DICT table in the gINT database then the AGS file will not have a DICT section.
That's exactly what I did, probably something else that I miss is wrong!
It is also possible that there is a bug in gINT causing the problem. I will add a non-standard field to a table and then update my DICT table. From other postings it looks like you are running the latest posted gINT build. I am not running the latest build, so I am not sure it that will help out much but it is worth a try.