--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:

> As a reality check, to determine whether this is an access problem particular to Windows 7, or just some mistaken assumptions about access to the security database on Fb 2 and higher, try the following:

Could it be mistaken assumptions about access to the security database on Firebird 2 when the same gsec call without piping and redirecting shows the expected information? To be honest, I don't think so.

> 1. In aliases.conf on the server, define an alias for the security database. On my (WinXP) system, on a server called "dev1" I have:
>
> sec = c:\Programs\Firebird\Firebird_2_0\security2.fdb
>
> 2. On WinXP, stdout behaves "normally" for a local shell. From the directory on the remote client where you have the **correct version** of gsec.exe, do:
>
> c:\Firebird\tools\bin>>gsec -database dev1:sec -display -user sysdba -password masterkey
> user name uid gid full name
> --------------------------------------------------------------------------------
> ----------
> SYSDBA 0 0 Sql Server Administrator
> BLIMEY 0 0
> REPL 0 0
>
> 3. Next, on the host machine, set up a share for the remote (from server) location where you want piped output to go. My server (dev1) uses a directory called "scratch" on a share that it sees as "drive T".
>
> 4. From the remote client's tools directory, do:
>
> c:\Firebird\tools\bin>gsec -database dev1:sec -display -user sysdba -password xxxxxxx > t:\scratch\output.txt
>
> And here is what output.txt looks like:
>
> user name uid gid full name
> ------------------------------------------------------------------------------------------
> SYSDBA 0 0 Sql Server Administrator
> BLIMEY 0 0
> REPL 0 0
>

I'll give that a try.

Mathias