> I have tried this, but it doesn't work. This is my situation:

> 1. I am using Windows Vista Business
> 2. I install Firebird 1.5.5 running as service

Classic or superserver?

> 3. I stop Firebird 1.5.5 service
> 4. I edit firebird.conf in privilege mode to avoid VirtualStore problem
> 5. I add "IpcName = global\FirebirdIPI" to firebird.conf

Try Global\... (I believe it is case-sensitive) Furthermore I think that Firebird 1.5 used a different IPCname by default (I think it was changed to Firebird in 2.0, but I am not sure; neither am I sure if it matters)

> 6. I save Firebird.conf and start Firebird 1.5.5 service again
> 7. I logon to an "limited user" account and access a firebird database
> using local protocol. I still get "unavailable database" using local protocol
>
> If I start my firebird in application mode (e.g: fbserver -a), I manage to
> access my firebird database using local protocol.
>
> What's wrong with my steps?

Not sure, I could give it a try at home tonight.

Mark
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01