The title I think covers it. We have been maintaining a maintenance package for many years and I am wondering if I am braking my license agreement if I use all of the current version 17 licenses plus a version 16 licenses?
If so, the answer is: no. See page 2, 3)d) of the EULA:
You agree that the upgrade or update does not constitute the granting of a second license to the Software (i.e., you may not use the upgrade or update in addition to the software it is replacing,
You mean you bought a perpetual 16 and then an upgrade to 17? But want to keep using both versions?
Several prominent members of the Community are under the impression that they don't violate the EULA if they hold on to all the licenses for testing purposes only. I didn't read it that way, but to settle the problem, I recommended the following Product Idea:
Change License Agreement to Allow Multiple Versions for Testing
It might seem that the spirit of the EULA is that if you paid enough to use 10 licenses,
then you should be able to use up to 10 licenses not matter what versions,
and having old versions should not be an issue as long as you never use over 10 licenses at a time or permit more users than are currently licensed.
However, to me, the letter of EULA does not seem to permit this.
Some of my clients use El Capitan, Sierra, High Sierra and Mojave and some have computers that can not update themselves (Mac Mini and iMac 24 ").
If I leave FMP14 or FMP15 on my old iMac computer that can not run more than El Capitan because of the Wi-Fi card and FMP16 or FMP17 on my MacBook Pro 15 "end of 2015 under Mojave, do you think I'm not in convenience with EULA?
I need both systems to maintain all my clients. I bought perpetual licenses and updates (since FMP3), I can let them live on my systems as long as they run.
It's the same for Windows between XP, Windows 7 and Windows 10, I'm forced to live with multiple PCs and several versions of Windows.
Just because Apple or FileMaker is releasing a new software version does not mean that all users are running into it.
Today, I work for a large customer who has a global fleet of 120,000 PCs being migrated from Windows 7 to Windows 10 and this is not done overnight. It took 4 years of preparation to ensure and stabilize this migration. On this type of client they have two versions of all softwares running together for more than 1 year and a half.
They don't use FileMaker they found to expensive and use Access, PostGresSQL, mySQL data bases and a lot of Excel files with Office365.
Retrieving data ...