ChrisConsider this scenario: A legitimate user installs my product and activates the product key on his computer. Let's say that there is only one activation available for him. If he wants now to switch to a new computer, he cannot do that because he will not be able to activate the product key on the other computer.
Would it be a good thing, to have a function in my program, that lets the user himself deactivate the key (on the server), so that he can then activate it again on his new computer? Or is there a better way to handle this? Of course he could always contact support to let them handle the deactivation, but I would think this is a smoother way, to avoid a support item.
//Chris
Would it be a good thing, to have a function in my program, that lets the user himself deactivate the key (on the server), so that he can then activate it again on his new computer?
Sure, it's already built into TurboActivate. Just call TurboActivate.Deactivate(). Also, the example Delphi project shows example usage.
Is this what you're looking for, or have I misunderstood you?
