--- In firebird-support@yahoogroups.com, Lester Caine <lester@l...> wrote:

> psmdev wrote:
>
> > We have some applications that have to launch on a completely
> > unattended terminal PC. We occasionally get a problem whereby our app
> > will try to connect, but the firebird server returns an error along
> > the lines of 'No Read/Write access to Database file xxxx.gdb'. Our
> > app already checks for a running process called 'Firebird Server' or
> > whatever, and that check get passed. If you just OK or Cancel on that
> > message and try again, it's fine.
>
> Straight after starting the machine?
> Windows takes awhile to get round to staring things, even after the

user

> interface is open, so programs that 'autostart' at start up fail unless
> you wait a little longer. I put a delay on accessing the database just
> to be on the save side.

Yup, Straight after startup. The App actually sits there looking at
running processes and waits for a firebird Server to appear, if it's
not already there, and goes through 3 login attempts, with a small
delay in between.

The odd thing is the message we're getting isn't the 'Unavailable
Database' one you get if the server isn't running at all - it's this
'No Read/Write Access' message, which refers to the physical database
file itself. Seems to almost suggest the file system itself hasn't
initialised properly, rather than Firebird.

Perhaps we should make it wait for a Firebird Guardian process, intead
of a Firebird Server one?