Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Using older version on elevatedb server...
Tue, Jun 30 2015 7:58 AMPermanent Link

Antonio Marques

Hello! Recently, we updated the version of ElevateDB on our Application but we have forgotten to update the version of the ElevateDB Server. No errors, it works normally.

The version of EDB on the application is 2.18 Build 1, on the server is 2.08 Build 3. The software is now deployed on hundreds of clients. Until now, no problems where reported.

Do you think we should make an emergency update to match versions?

The clients will continue to use older sofware that uses 2.08 Build 3 version to connect to the server, is there any problem when a older client connects to a newer server?

Thank you!
Tue, Jun 30 2015 8:25 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Antonio


>Hello! Recently, we updated the version of ElevateDB on our Application but we have forgotten to update the version of the ElevateDB Server. No errors, it works normally.
>
>The version of EDB on the application is 2.18 Build 1, on the server is 2.08 Build 3. The software is now deployed on hundreds of clients. Until now, no problems where reported.
>
>Do you think we should make an emergency update to match versions?
>
>The clients will continue to use older sofware that uses 2.08 Build 3 version to connect to the server, is there any problem when a older client connects to a newer server?

Its good practice to keep the client and server in sync but wether or not you will have a problem depends on exactly what bits of ElevateDB you use. In very general terms a new version of ElevateDB is either a bug fix, minor improvement or major new feature. Sometimes there are breaking changes and those are the ones that may catch you.

Looking at the release notes there are quite a few breaking changes between 2.08 & 2.18 You need to review those yourself and work out if any could cause a problem if so you need to upgrade. Personally since there are breaking changes I'd err on the side of caution and upgrade.

Roy Lambert
Tue, Jun 30 2015 9:21 AMPermanent Link

Antonio Marques

Ok. Got it. In relation to the last question, when we upgrade the server, is there any problem if users connect to it using older version software? (versions mentioned above)
Tue, Jun 30 2015 11:11 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Antonio

>Ok. Got it. In relation to the last question, when we upgrade the server, is there any problem if users connect to it using older version software? (versions mentioned above)

Its the same answer - its best to keep client & server software in sync.

Roy Lambert
Wed, Jul 8 2015 11:54 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Antonio,

<< Hello! Recently, we updated the version of ElevateDB on our Application
but we have forgotten to update the version of the ElevateDB Server. No
errors, it works normally.

The version of EDB on the application is 2.18 Build 1, on the server is 2.08
Build 3. The software is now deployed on hundreds of clients. Until now, no
problems where reported.

Do you think we should make an emergency update to match versions? >>

The only possible issue that you can encounter is the situation where there
is a new feature/fix in the client call-level API that can't be used
correctly because the client isn't communicating with a newer EDB Server
that has a corresponding new feature/fix.  Both sides of the EDB
communications know the version/build of the other side, and will only
communicate in a way that the other side can understand.

There were a few such feature improvements/bug fixes between 2.08 and 2.18
that fall into this category.

Tim Young
Elevate Software
www.elevatesoft.com
Image