Mainly it depends of the level of trustworthiness and knowledge of these users how and with which efforts you could implement such logic. It just based on the access-rights to the qvd's and at least one mounted qvw-folder.
In the simplest case you give them just the access-rights and they could loading data and creating qvw's like the want quite identically as if they would work directly on the server - a bottleneck in this scenario (beside security considerations) could be the probably slow network-traffic compared with the local storage of the server.
We use a quite similar scenario and the waiting-times by the larger qvd's/qvw's is quite significantly - but in this way I could ensure that all data are always up to date. Otherwise I would need logics which copies the data and applications from the server to the local machines and back again - regularly and/or on the demand - which is in generally possible but not really trivial to implement and would consume a lot of traffic to transfer everything to and fro.
From this as a starting point you could make it more complex with specific folders or maybe even an own server in between the qlikview environment and these local users and more or less redundant data more or less permanently synchronized with tools like robocopy.
The licencing topic is probably the easiest one because the users could lease them from the server. A single licence meant two accesses for example one with the access point and the other within the desktop client (needs to be refreshed all 30 days).
- Marcus
