Hi Richis,
If I understand you correctly, your databases are located with your application on install. When you change your install location with GP install, the database location is unknown in the app.
Unfortunately, GPinstall is free, and not supported by its authors - for obvious reasons. However, given that, it does have some solutions to most of your problems in the help, and with a little playing about.
Might I suggest that you firstly set up the app to open the databases from a configurable location (stored in an INI file or the registry)
How to setup and use an INI file can be found in the help on [tt]tINI[/tt]. You can set up an INI file, with the appropriate section and value, in GPinstall (there is an INI file dialog - you need to make a new file, and add the section and values required). Another scenario might have the user configure the app on first use, but thats not too hard.
Alternatively, and perhaps more elegantly, you can use the registry, and write directly to that from GPinstall (use the Registry Dialog), and read it using [tt]tRegIniFile[/tt].
In both cases, the help briefly describes the method, including inclusion and expansion of standard variables like [tt]<SOURCEDIR>[/tt] and [tt]<INSTALLDIR>[/tt] etc
As for adding database modules, you need to write a DLL for the purpose -
remember GPinstall is not InstallShield or any of its variants. A demo of installing the BDE is on the GPinstall web site, but could probably be adapted for your purpose.
Finally passwords - not sure of your problem here. However my password solution is to use a registration password in the app itself using a neat (and free) component called [tt]TmRegApp[/tt]. Its fairly hard to break as the GUID for the app is randomly generated, and the activation key is encoded. You can get that from:
Good luck!
Chris ;-)