Jeffrey Kain jeffrey.k...@gmail.com<mailto:jeffrey.k...@gmail.com> writes:
>Nope... >If 4D makes a major change to the protocol they'll block it. For deployment >we try to have matching versions always. > >> On Aug 28, 2018, at 2:24 PM, Dave Nasralla via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> One of our systems is developed with 4D Server (Team Developer) with >> several coders connecting to make changes. If I move the Server from, >> say v17.0 to v17.0 HF1 or a nightly build, do all the other developers >> need to update their versions? Ditto here. For Deployment we always match clients to server versions, even down to the build number. Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
