Any common wisdom on reasonable approaches to lisencing a VB App written for the medical profession.

I amm assuming that by and large, the potential customers are honest folk who are not adept "hackers". I would consider even the simple changing of the system date to start the app then changing it back after it is started a "hack".

I have some ideas which all end up relying on an individualised license file (probably just a small dll) which require the user to run a license app on their machine, call a support centre to give them the auto-generated code, which the support staff use to generate a license file which is then emailed.

The problem is: It's all sounds a bit too reminiscent of *some* programs that generally everyone hates.

I am certain that some of the experience developers out there have a few ideas, and I'll bet there are even custom controls I can hook into that do it for me!

Any clues are welcome. Any advertising of your own modules is also welcome. I'm in the market

Cheers
Paul Lewis
[email protected]