Couple of ideas. First, let's review how the licensing works. The program don't care how many users are using the database at one time, known as simultaneous use licensing. That is not how licenses are counted. (This is a common misconception, and why I am taking the time to address it now.) Licenses are assigned to a COMPUTER when that computer first accesses the program. This is a semi-permanent assignment in that the license will remain assigned to that computer until it is manually released. Thus, in your instance, two computers are requiring two licenses. I suspect what you have done in the past is load/install the entire program on both of your computers, giving you TWO Timeslip.CFG files. In the older Paradox/BDE versions of Timeslips, these Timeslip.CFG files were the "license cops." They manage the licenses purchased/available, and what has been assigned to which computers. Again, if my suspicions are correct in your scenario, each computer then had it's own CFG for a single license, and assigned that license to itself. If you ever tried to use the same database on the two machines simultaneously, you would have gotten an error as those license files conflicted with each other. However, as long as you only tried to use one at a time, the setup allowed you to do so. The new 2017 database is a Firebird SQL database which still assigns the licenses to computers (again these are not simultaneous use licenses), but is much more centralized about it. It assumes the database is located on the same machine with the single license. Hence, your needing to copy. So, what can you do? 1) you could buy a second license to allow two machines to access the same database, but I wouldn't in this scenario. Instead, I would 2) look at setting up a remote desktop connection between the two machines (free if you use the Windows remote desktop tool) and simply "drive" the one computer with the license (the primary) from the other (the laptop). See: support.microsoft.com/.../windows-7-connect-to-another-computer-remote-desktop-connection What NOT to try: storing the database on some sort of synchronized database location such as Dropbox, etc. That will eventually lead to corruption, and nobody likes corruption. Hope this helps.
↧