Hi Artur,

> If everyone follow the rules for client/server deployment, you
> shouldn't have any problems deploying your application: just
> ask for the sysdba password and you're ready to go.

Yes, _if_! But others don't and I have the trouble with it. As stated
before, there are some other companies that set a modified sysdba-password
while installing and don't tell me (mail, phone,...) or the customers what
it is. They want to protect their Data! I was able to crack one of them but
there are others out there.

> We have a bad story with applications that 'register' the server and the
> dtabases. Remember IBConsole? There's a lot of people that still asks on
> support list how to register the server to be used by there own apps.
> ...

Ok, I think you are right. A concept like this would require that every
other company follows the rules (register at installation time, unregister
at uninstallation time). But if they would follow the rules we had no (lees)
need to have this conversation :-)

>...
>> As I explaned/showed before the main problems are the non-dedicated

servers.

>
> Let it be. Firebird is so small that it will not hurt any hard disk space.

Yes, it's small and doesn't hurt but - sorry - you don't understand my
problem. It's not mainly the uninstallation - it's the _installation_. I
don't uninstall Firebird while removing my application!

I see/have two major problems:

1. Different, incomatible Versions of Firebird/Interbase.
Some Customers have already a IB-Version installed - but a different
version. I can not guarantee that FB-Server 1.5 works with all applications
build for 1.0.3 or specially Interbase 6.0 Open Source (ambigious
references). The incompatibility between different Versions are not
acceptable to me. A higher Version should always be able to handle minor
Versions (sorry, don't know the right words in english). So every party
could always install the newest version and no other app gets corrupted. We
never need to install two different FB-Servers on different ports,...
But at the moment it's not reality - so, back to the initial idea, I wanted
to try some kind of mix between embedded and C/S-Version. But some of you
told me that this shouldn't work :-((

2. Modified _and_ secret sysdba password.
I don't change the sysdba password. As long as everyone can replace the file
and has full access I don't think that this makes sense. I only add a extra
Username to be independend from later changes of sysdba-password.

I agree with you: we should follow the rules! But the others don't. And we
have to handle it.

With regards
Thomas