Exporting to custom gINT databases

Navigation:  Exports and Outputs > gINT >

Exporting to custom gINT databases

Previous pageReturn to chapter overviewNext page

Many gINT users have customised their own database structure within gINT for their own specific purposes.  If this is the case then the gedt export from ESdat will need to be edited to match the custom database structure.


To do this you will need to following files:


Your .gdt (gINT Template) file.

Your .glb (gINT Library) file.

An ESdat gedt file (handles the translation between the ESdat database and the gINT database, similar to a gINT correspondance file)


Construction of the gedt file will need to be done using a text editor, such as notepad.  Users can either start with a blank file, or modify one of the gedt files for the standard gINT databases.  The format of the gedt file is given in the section on the gedt format.  Gedt files for Access based systems should have a .gedta extension.  For SQL Server systems they should have a .gedts extension. Gedt files can get complex, and your support contacts may be able to assist on a consulting basis.


Once completed, the three files mentioned above should all be given the same names (ie "custom1.gdt"; "custom1.glb"; "custom1.gedta") and placed in the same ESdat template directory.