Hi,

sorry being late to answer...

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> Yup, there are myriad variations (I've discovered some more, as well)
> that at least demonstrate that the logic is broken in v.1.5.3. It's
> being looked into.
>
> Are you getting identical behaviour with both v. 1.5.2 and 1.5.3?
>
Yes, exactly the same behavior with both. I have no difference between
local and remote connections. I've made some more tests, and I think
the bug appears when using a user different from sysdba and the
current database's owner.

My tests :

C:\>gbak -c c:\donnees\employee.fbk c:\donnees\employee.fdb -user test
-password test
(**** not as expected *****)

Trying again with the new database's owner :

C:\>gbak -c c:\donnees\employee.fbk c:\donnees\employee.fdb -user test
-password test
gbak: ERROR: database c:\donnees\employee.fdb already exists. To
replace it, use the -R switch
gbak: Exiting before completion due to errors
(as expected)

With sysdba :

C:\>gbak -c c:\donnees\employee.fbk c:\donnees\employee.fdb -user
sysdba -password masterkey
gbak: ERROR: database c:\donnees\employee.fdb already exists. To
replace it, use the -R switch
gbak: Exiting before completion due to errors
(as expected)

With a new user :

C:\>gbak -c c:\donnees\employee.fbk c:\donnees\employee.fdb -user
test2 -password test2
(**** Not as expected ****)

B.L.