> 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.

If you take proper care of your transactions and have forced writes set (default with Firebird), restarts should not be that much of an issue (well, if you have 100 employees connected and a server going down 10 times a day, they will get irritated). Sure, you lose what has not been committed and those that were connected at the time the server went down will have to reconnect and they will also lose what has not been committed, but the Firebird server could start as a service and corruptions would not normally occur.

Set