You know, this reminds me of when I used to manage restaurants. I'd tell my managers that a place runs better when it's easy to do the right thing and hard to do the wrong thing. So you really want to avoid making it easier to do the wrong things. Because the easier something is to do the more likely it is to get done.
On Wed, May 9, 2018 at 2:52 PM Wayne Stewart via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Hi > , > > Just some more clarification on licensing. > Not many people read the fine print of the license. > > A > 4D Application Single User (or what many people call > engined > or > sponsored version > ) > can’t > connect more than twice per day to write to a data source. It can > connect as many times as you like to read from it: > > > LICENSEE recognizes and agrees that the access to one or several remote > server(s) through 4D Application Single User is authorized, provided that > this 4D Application does not modify this/those server(s) and its/their > data. Notwithstanding the above provision, 4D Application Single User may > permit the reading and/or occasional “batch” update of the above mentioned > server(s), and this, within the limit of twice (2) every twenty four (24) > hours. > > As a standalone you need to be using 4D SQL DESKTOP in order to connect > more than twice a day to a data source for writing. > > A SQL Desktop can connect using web, web services, SQL, anything at all as > often as you like. > > As Tim points out what it connects to needs be licensed appropriately. > > I'm not certain how remote datastore connections will work in v17 but I'm > sure a lot of people had a lightbulb moment thinking I could use that for a > remote standalone (*and it will be great for that*). > > However, unless 4D changes the license you won't be allowed to do that from > something using only the 4D interpreted or unlimited desktop licenses. > > I hope that's clearer (but I think I've just muddied the waters rather > than anything else). > > Cheers, > > Wayne > > > On Thu, 10 May 2018 at 06:13, Timothy Penner via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > > > > If you use SQL there is no additional licensing needed. > > > > This is incorrect; or at least it is misleading... > > > > If using SQL, and you do not have an "Unlimited SQL License", then each > > SQL connection will consume a Client License on the 4D Server. > > Therefore, if there is no more 4D Client licenses available on the 4D > > Server then the SQL connection would fail. > > > > The best approach if your 4D Server is serving SQL Connections is to > > purchase an Unlimited SQL License: > > http://www.4d.com/products/4dv16/4dsqlexpansion.html > > > > -Tim > > > > > > > > > > ********************************************************************** > > 4D Internet Users Group (4D iNUG) > > FAQ: http://lists.4d.com/faqnug.html > > Archive: http://lists.4d.com/archives.html > > Options: https://lists.4d.com/mailman/options/4d_tech > > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > > ********************************************************************** > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** -- Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
