I wrote a tiny QV app which loads data from a special source and provides the data as QVD file for further processing. The special source is on a special machine, so I installed QV and let the QV app run/reload regularely triggered via WinAT/ batch. This works fine.
The QV installation on that special machine needs a license, so I connected to our server with a specially created account and got a license assigned to that special user. The client shows 'you are currently leasing a license from xyz'. Still all fine.
As I understood license lease, the user can keep the license for max. 30 days, latest at that point the user must connect to the QV server to refresh the license.
In my scenario, there is no need to connect to the server (as the QV App runs locally), and there is actually no real user (just WinAT/ batch). Somehow I am afraid that in latest 30 days my process will stop working due to a missing license.
Am I right, and if so - what could be a possible workaround (besides having me manually connecting every x days 😉 ? I thought about opening a 'dummy app' in the batch on the server just for the sake of refreshing the license, but before I do that I would like to know if this is really necessary.
I believe that is indeed what will happen. Leased licenses are only valid for 30 days so you will need to reconnect to the server at that point, either manually or with your dummy app. From a licensing standpoint, this makes sense or else everyone would just connect once and then be able to use QV for free...
Somehow I was hoping that QV (V9 SR2) does the license refresh automatically in the background, even without the need from my side to explicitely connect to the server (with the dummy app). In theory, the client knows where it got the license from, so on startup it could refresh the license.
