They are Set to auto. None of our apps are services - Just standard
apps, although a couple just sit in the system tray.

If we didn't launch stuff at startup, and just relied on manually
launching the stuff, there is no problem. Since FB is supposed to be
running as a service, it should be completely up and running before
you've even logged into windows - This is what makes me think it might
be the guardian's fault, as I think that runs as an app, rather than a
service, so it's not launching the FB Service until after windows is
logged in and it starts?

We're going to do some experimenting... another thing is that we never
had this problem with interbase 6 Opensource.

> Make sure the start up type for FB Service and Guardian are both set to
> Automatic.
>
> Is your app a service application? If so make sure that it includes

FB in

> its list of dependency services as well as TCP/IP if that's what you

use for

> your connection method.
>
> hih
>
> Si Carter
> http://www.tectsoft.net/