This definitely works for versions within a main version number (ie, anything in v18). I haven't tried it for major version number updates (eg v17 to v18).
Pat On Wed, 13 May 2020 at 14:39, Eric Naujock via 4D_Tech <[email protected]> wrote: > I have an interesting question that doe snot seem to be clear from the > documentation. > > If I build a Client server application in 4D using v18.1 and then after > deploying I make a client /server version using V18r2 will the clients > built under the v18.1 upgrade from the 18.1 base code to the 18R2 code > automatically? Or will I need to release a new client application for the > users. I relish it is ideal to release the new 18r2 version for new > deployments but can you do this with a major jump from 18.1 to 18R2. Or > even to take it further go from 17r5 to 18R2 using the client server update > mechanism. > > I know the documentation says that if I build the client server app using > the right components and check for upgrade clients it will do this for a > minor upgrade like 18.0 to 18.1 but some of the other bigger upgrades it is > not clear. > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > New Forum: https://discuss.4D.com > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- ************************************************* CatBase - Top Dog in Data Publishing tel: +44 (0) 207 118 7889 w: http://www.catbase.com skype: pat.bensky ************************************************* ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
