Kjell, I can't tell you how much I appreciate the thought (and effort) you have put into your answer. You really are a great helper. Thank you.

I've tried to think of everything that must go into a tool such as I would like to build. Your insight is a big help.

The procedure you've outlined is very similar to how I handled my installation for my old Access version of the software (prompt user for Stand-alone computer, network server, network client). With Firebird, however, I feel I need to avoid using "embedded" even for a single user installation. Most of my customers have multiple users. The only ones that don't are new insurance agents who can't afford staff. As they grow, they usually add staff. Most of the time, they don't add a dedicated server when they hire their first employee, so the first stage of their evolution is usually a peer-to-peer setup.

My thinking is, that in a peer-to-peer system, the original computer will use "LOCALHOST" as the server, and the new, additional computer will use the host computer name (rather than the IP Address). I have already created a Data Path Configuration utility that uses a directory tree for the user to "find" the .FDB file via the network. Once that file is found, the utility records the host name and data path in the Windows Registry so the main application can act accordingly. In my local testing, this works very well, and is quite intuitive.

My pre-release (pre-alpha) installation program asks the user to identify what kind of installation is being done (server, client, etc). If "client" is selected then only the application and support files are installed. When the install is finished, it launches the Data Path Configuration utility. BTW, I keep the Data Path Configuration utility installed in the event the server needs to be changed (they out-grow a peer-to-peer system).

You have touched on the problem I am now trying to solve, which is what actions to take when the user selects a Server installation type. Right now, my setup program just launches the standard Firebird install. As you've pointed out, that isn't good enough for all situations. Today, I'm trying to figure out if I can accomplish the things you've suggested by using command line switches, or if I need to create my own server install, or if my only choice is to write really good instructions (and pick up the pieces via remote access if they don't follow them).

My goal is to help my users to be as self-sufficient as possible. That makes their life much easier, and it keeps my phone from ringing.