On Mar 6, 2006, at 09:25, Woody wrote:

> Whenever I write an app that uses the embedded server, under
> program options
> I supply the user with a checkbox. They select whether they are using
> standalone (embedded) mode or network mode. I then display what is
> needed
> for either mode based on their choice. All information is stored in
> the
> program .dat file so the program can read it when starting and know
> which
> way to go. Maybe something like that could help you with your design.

I was speaking rhetorically - sorry if that was not clear. We
actually have dialogues like that for some of the databases we
support (MS Analysis Services comes to mind).

The point was more that there is a UI/user education hit for such
decisions. In our case, we are not even sure if we want to support
Firebird servers at all because of issues like UI costs, regression
costs etc. It would be nice, but unless our users ask for it, there
is not much of a case for cluttering up the UI, adding manual pages,
adding test plans yada yada yada for something that no one has asked
for.

Along those lines, the OP also assumed that the users of an
application employing embedded Firebird even know what Firebird IS.
Most of ours do not (I was the only member of the dev staff who had
even heard of it) so for us right now, the case for supporting it in
the short term is pretty weak. I personally am pretty jazzed about
it, but right now is not the time for us.

Richard Wesley
hawkfish tableausoftware com