Helen Borrie wrote:

> But 2.1.anything to 2.5.something is a full version shift, with migration issues you would need to deal with anyway. The old client would probably still work, but why wouldn't you deal with the version mismatch along with the other migration issues?

Just to expand that point ...
If 2.1.x is running stably then I'd recommend sticking with it. It is probably
worth TESTING your applications on 2.5, but I suspect that you will find there
are 'migration issues' that will need to be handled. I've got a couple of
set-ups that run older code, and 2.5 is a bit of a brick wall until I can
recompile that code! ALSO 2.1.5 is at RC stage ... it's probably worth going for
that rather than rushing 2.1.4 out everywhere.

Helen is right about updating the client, but 2.1.1 does run and is not giving
me any problems. So something to filter in over time rather than looking to a
mass upgrade. Managing what is running on the clients is important if only to
pick up when a problem does happen that it may be due to the older client software.

2.5 however may well require a complete update of clients and applications and
all that rolling that out will entail :(

On many of my 'windows only' sites we now run Linux on the server(s). The
performance improvement over the windows servers is noticeable - but more so on
the web server side than Firebird. Linux is all 64bit, but the windows client
base in some cases is still running 32bit W2k ... Moving the clients to web
based has removed the management problems ... Just have to cope with all the
niggles browsers introduce instead ;)

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php