spikepl
Eledittingent Beliped
- Local time
- Today, 01:15
- Joined
- Nov 3, 2010
- Messages
- 6,134
We have an Access application which we may want to sell. Various payment models are being considered.
We need a mechanism to secure the application, meaning:
1. Application runs when valid license (limited validity, also one of unlimited validity) has been issued
2. Application ceases running, when there is no (longer any) valid license
I have not done such a thing before and can imagine an number of different solutions.
Any recommendations?
I don't want to reinvent the wheel. Maybe there already is some "licensing app" out there... I can make whatever needs to be made myself, and so would appreciate pointers as to what, sensibly, "needs to be made". The intent is to keep it as simple as possible both for us and for the customers.
TIA
Update:
The issue is of course not unique and some good suggestions come up when inspecting "Similar Threads" a the bottom of this page after posting ... I'll have to digest those.
We need a mechanism to secure the application, meaning:
1. Application runs when valid license (limited validity, also one of unlimited validity) has been issued
2. Application ceases running, when there is no (longer any) valid license
I have not done such a thing before and can imagine an number of different solutions.
Any recommendations?
I don't want to reinvent the wheel. Maybe there already is some "licensing app" out there... I can make whatever needs to be made myself, and so would appreciate pointers as to what, sensibly, "needs to be made". The intent is to keep it as simple as possible both for us and for the customers.
TIA
Update:
The issue is of course not unique and some good suggestions come up when inspecting "Similar Threads" a the bottom of this page after posting ... I'll have to digest those.
Last edited:
