Helen remarked:
Some days ago, one (or was it two) people advised you to use
TCP/IP. TCP/IP doesn't have these limitations. Please try the TCP/IP
protocol for your database connection and report back. Rename the database
file, then copy and paste the following into the client's connection string:

newserver:c:\prax\Prax.FDB

Well Helen, this is the manner I have always done my naming of paths, but
this doesn't work at all now, thus I reverted to the named pipes. I just
didn't want to throw all the eggs into the basket at the same time, thus as
I could get a connect with named pipes, I was getting closer to the problem.
When I use newserver:c:\prax\Prax.GDB .. I get error: "unable to complete
network request to host "newserver". Failed to establish a connection.
Unknown Win32 error 10060"

I will go and change to *.fdb and all other suggestions and then get back to
you again.

Thanks

Adrian