Tom Conlon wrote:

I'm not clear on the above and anyone that can give me any 'definitive answers' then much appreciated.

One time the considered advice seemed to be that always keep your client DLL version in synch with the Server - DB corruption could potentially result otherwise.

However, some time recently a post stated that the newer client DLL should be backwardly compatible.

My problem is that I have to update 1 legacy site (from v1.52 to v1.53 initially) - 70 users over 2 locations. The network manager keeps his network very 'locked down' and he says he will have to go around all 70 machines, log on as administrator and update the clients. I'm aware there are other ways of doing this but he has his reasons...


  1. Is it ok to ugrade the server to v1.53 and leave the clients?
  2. I'll be going go v2 when prudent to do so, any actions to take now or do differently when that time comes?

Vlad Horsun answers:

FB 1.5.2 clients must be fully compatible with FB 1.5.3 server.

We support as much compatibility between old and new clients and servers as possible. So i expect using 1.5.x2.x clients with any 1.5.x 2.x server is OK. If it is not so - it is a bug needs fixing. So far i not aware of such problems.

There are however some _documented_ incompatibilitiesside effects in regards of using different client and server versions :

  1. local protocol is not compatible between 2.x server and older clients (i.e. before 2.0) it must be not a problem at all as server installation includes right client library
  2. changes in remote protocol in FB 2.1 can have some side network performance effect if old client used with 2.1 server. This effects can be both negative and positive

Like this post? Share on: TwitterFacebookEmail

Related Articles


Firebird Community



Gems from Firebird Support list