Assign gINT library to project


I was wondering if there is a way to assign a library to a particular database project.  For instance, when someone opens project ABC the correct library (libraryABC) opens up with the project file rather than having the user choose the specific library?  Could this be done with gINT rules? or is there some built in function to help with this? 

Although ideally we would have one library, the fact is that over the years people have developed small changes and made a new library for almost every project.  I know this is poor database management and we are moving towards using just library on all new projects... but we haven't figured out a way to effeciently compare library files for difference in report design and look up options.. any ideas on that as well?

Any help is greatly appreciated.


Kari Weber

  • Hi Kari,

    Please only follow the instructions below if you understand and are comfortable with the system properties settings in gINT.

    Each time gINT starts it looks to the setup.gsh file (which should always be stored on your local system). This file records your System preferences as well as the last library, project, application tab, etc, that you accessed in the last session in which gINT closed successfully. To know where your setup.gsh file is stored to go Help>About gINT and you will notice it is specified somewhere on the top of the resulting dialog.

    To solve your problem you can create multiple gINT shortcut files on your desktop (or wherever you want on your local system). Each shortcut will be associated to a different setup.gsh file. That way, each time you open gINT from one of these shortcuts, it will default to the settings from the previous session in which you used the same shortcut to start gINT. Here are the steps to do this:

    1. Go to the gINT shortcut on your desktop. If it does not exist then create one by dragging and dropping it from your windows Start menu.
    2. Make a copy of the shortcut and give it an appropriate name so you will know what it is for (i.e. a certain project name). 
    3. Create a folder on your local system with an appropriate name so you will know what it is for (i.e. the same project name from step 2). Always use a different folder for each different shortcut file you will create.
    4. Right click the newly named copy of the shortcut file and select Properties. Click the Shortcut tab and put your focus in the Target field. You will see something like this: "C:\Program Files (x86)\Bentley\gINT V8i\bin\gint8.exe" 
    5. To the end of this string add the following text with a space in front of it /setup = "<<path to the folder you created in step 3>>" Within the quotes put the full path to the folder without the <<>> characters. 
    6. In the Target field your shortcut properties you should now have something similar to this "C:\Program Files (x86)\Bentley\gINT V8i\bin\gint8.exe" /setup = "C:/gINT/new folder"

    The first time you open gINT using the newly created shortcut, a new setup.gsh file will automatically be created at the location you specified in step 5. Therefore the program will behave as if you are starting gINT for the first time and prompt you for system properties settings, company name, etc. After the first time however, whenever you use this shortcut to open gINT it will remember the library, project, system properties, etc, from the last session in which you used the same shortcut file to open gINT. All this information will all be stored in your new setup file.

    You can have as many setup files as you wish. They should all be stored on your local system. If the path changes (because you renamed a folder for example) and gINT cannot find a setup file, it will automatically look for the setup file you used previously until it finds one. If it does't find one it will create a new one and once again behave as if you are opening gINT for the first time.

    If you want t be sure you have actually created the new setup file, then follow the instructions above, then open gINT with the new shortcut file. Browse to the folder you created in step 3. You should see the file setup.gsh, and if gINT is currently open you should see a second file setup.ldb. 

    Please let me know if this resolves your issue.

    Good luck & Best Regards,


    Johnny Martel

    Geotechnical Data Services 
    gINT Software Specialist
    Tel +34 617-217-012
    Los Angeles, USA
    Barcelona, SPAIN