Are there any problems running newer clients against an older server and vice versa?

I have a couple of old apps in the field that were created with DBISAM 4.22.  I plan to update to the latest version of DBISAM, but need to plan the update.  

For the local app it is a matter of making sure that data which has been written to by a new version can't be opened by an old version so as to avoid the BLOB corruption that would otherwise ensue because of the changes made in 4.28.  I have a plan to prevent this, so no problem.

For the client-server app, however, what are the issues.  If some of the clients update but not all, will it still all work with new clients accessing the old server?  If I then update the server, will it still work with the odd 4.22 client accessing the new server?

Bill Sparrow

Bill,

<< Are there any problems running newer clients against an older server and
vice versa? >>

From a "will you get an error" perspective, no.  However, there are some
client-side fixes that can affect the server, and vice-versa, since 4.22, so
while it can be done, it is usually best to get them to match so as to have
the latest fixes for both ends.  Of course, I understand that sometimes this
cannot be done simultaneously, but the ultimate goal should be to get both
ends on the same version.

<< For the client-server app, however, what are the issues. >>

As far as the BLOB architecture change, there aren't any issues with a
client-server set up since the DBISAM Database Server is the only process
ever reading/writing to the tables.

--
Tim Young
Elevate Software
www.elevatesoft.com