Hi Robert,

> The Install components (TIBInstall) are to install Interbase, is that
> correct?

Yes.

> So what is the scenario:
>
> Install your app. If initial install of app then call to a set of
> Interbase install routines within app?
>
> Or, have separate program to install IB, with a RunOnce with Restart
> set in the app install?
>
> Or ????

AFAIK, both ways are possible. The one you should go is completely up to
you. For example, I run a special program written by myself from my
InstallShield script, and this program installs IB via TIBInstall.

> This is not clear to me. Especially:
>
> From Help-
>
> Executes the installation.
>
> void __fastcall InstallExecute(void);
>
> Description
>
> Call InstallExecute to execute the installation.
>
> Note: You must install InterBase 6 to use this feature.
>
> The "Note:" above implies that IB6 must be installed to use the install.
> Do not understand this comment?

The only requirement is that a root folder of IB distribution must be in
the search path. TIBInstall class incapsulates Install API calls, and the
code of these routines is within ibinstall.dll which is located in the root
folder of IB distribution. So this DLL should be accessible for your
application.

In my case I append the IB initial location to the PATH variable, then
create an instance of TIBInstall class and do the IB installation. After
that I remove the initial path from the Windows environment.

If you're interested more, feel free to ask. I've got this stuff working
and there's no problem for me to help someone else.

Best regards,
Dmitry