> Yes of course but in my case some of the other applications automatically
> change the sysdba-password and my customers don't know that changed
> password! So nobody at the customers side knows the password and I can't add
> my user/password or even login!

That seems to be an problem in these other applications - tey should
at lease document that they require an exclusive instance of FB.

> But if I refuse it, what's next? They'll call me and i have to solve the
> problem. As the different versions of Firebird are not compatible with their
> prior versions I can not tell them "Use my Firebird Version (1.5) and
> everything will be ok". If the other app uses Interbase they can run into
> the changed behavior regarding "ambigious references"...

In daubt your application should guid the user to install an separate
instance of FB.

> For example: If they install Superserver Version 1.0[3] after my 1.5
> (clientsetup) the Setup don't overwrite the system32/gds32.dll because it's
> newer. But the firebird.msg will be overwritten and so doesn't match the
> DLL.

You can place both files to your application directory.

> "should be"? What about the firebird.msg-file? Is it needed?

It is needed to decode error-numbers only.

Elmar