>I am rewriting an old program that uses Access and the new one uses Firebird.

I am happy to see that I am not alone.

> You might even instruct users to install the server in another computer: I don't thing that our programs are very demanding for today's hardware, so the server might be installed in any computer in the network.

It sounds as if your users are setting up Peer-To-Peer systems. Even though many of mine do to, I have always encouraged them to use a dedicated server computer. Perhaps that is less important with Firebird than with Access. Even so, on Windows computers, the OS often needs to be restarted. That's not nice if that computer is also the Firebird computer. That is a real problem with my app, because the typical user starts the program in the morning, and continues to use it all day.

> Here customers with a small network do not have an IT staff, but they have somebody to ask for help. Usually they call guys from a nearby computer shop, the ones that sold them and set up the hardware.

Those people probably do not have experience with Firebird, but they
should be able to understand simple instructions about configuring an
existing server to handle also your database. So writing a page
explaining how to set up an existing server might be a good idea.

Most of my customers are exactly like this. Many of the "computer store technicians" are pretty good, but some are not. The ones that are not, tend to think they know more than the application developer, and try to do things their way. Those are the people who create headaches for me. That is why I try to make my application, including my setup program, do as much as possible. The more I can automate, the fewer mistakes I need to fix fix. Just my personal opinion.