Question Locked

Need to create a license file for homegrown app

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a 10 year old homegrown Access application that we provide to customers at remote locations, mostly nursing homes. When we lose a customer (they decide to use a different distributor), we need a way to remotely disable the software. I would like a way to create a license file that they need to update at certain intervals, or other suggestions on how to accomplish this goal. The application was created with Access 97. We actually own some of the computers. So with those specifically, I have considered using something like "Logmein" to remotely access and simply alter the executable. But on the ones that we don't own, does anyone have any suggestions?

6 replies

by thumbsup2

If your original distribution of the app did not include a terms of use agreement specifically stating that they can no longer use the app when they leave your services, you're out of luck. I don't believe that adding it after the fact wouldn't be legal.

You can consider adding specific terms of use to any apps distributed from this day forward and look for a way to limit use by registering with you on an annual basis. But, your previous distributions are probably just "gone".

by tcheche

...is mainly what I am refering to. The problem is we can tell the customer "you can no longer use our program". And there is nothing stopping them from using it. We are not a software company. We are a food distributor. And if we were to take legal action, it may hurt us down the road when we are trying to regain them as a customer. But if the software were to simply stop working after a certain time, it wouldn't be as much of an issue. They call for support, and we say "sorry, we don't support non-customers." So I guess what I need is what you mentioned...A way to limit use through registration.

by thumbsup2

You said yourself, you're not a software company. What you're wanting to do is going to require someone developing a new application for you. You can then send the new app to new customers and gradually update/switch your existing customers over to the new system. Once they're all switched over, simply stop supporting the old system.

by sreenu.ps

We developed our product and its working fine but recently we got know that Some of our employes using our software and installing at client places so we are planning to Create License files for our product basically we create setup files its an .exe file and install at client systems. we have vb and vb.net developers so I want create the license files for user wise anybody can suggest some good method to create the same

by seanferd

License files are just text files explaining your licensing model.

Restrictions on installation can be accomplished with an installer kit - use a different installer builder if the one you use doesn't have options for license keys.

Restrictions after the fact are basically all legal, unless you want to get involved with authentication servers and/or DRM of some sort.

This discussion is closed to new replies.