>
>You may also want to save a copy of the real firebird.conf somewhere but
>the need to do that will depend on what kind of market you are in, who
>your users are and what changes you are making to the conf file.
>
>
>Paul

Well, I've been thinking about that. The particular application I am
wanting to use this for immediately is an application that interfaces
directly to a hand held device. This device takes ultrasonic readings from
things like machine bearings, but has limited storage ability and little /
no display ability.

So what the app does is send a command to the reader, download the
information, put it in a IB DB, and allow the user to display, print,
export and do some settings on the hand held device.

The particular nature of this application is such that while users might
sometimes want to connect the app over the network to see the data,
generally it will be a single user app on a single machine, belonging to
whoever uses the hand held device. I hope I am explaining this OK. The
environment is an engineering environment, and so the primary requirement
is for stability and robustness.

It (IB) has performed EXCELLENTLY in this regard. In the four years I have
been supporting / developing the application, I have NEVER had a complaint
about the database, or about database corruption. The closest I have come
to a complaint it "oh, but it's not SQL Server." There are over a thousand
sites world wide.

I suspect that FB will do even better. I have been thinking about the
nature of the app, and I think what I will do is give the client a version
which uses the default config file, and see how that goes. If there are
complaints, requests, etc., then I will handle them as they happen.

Any comments?

Regards

TIA

Tim


[Non-text portions of this message have been removed]