Password reset or book disable?

Any ideas?
Sincerely,

 That's not a bad idea.  I like the way you think!

 The only obstacle is to make that disabled state persist the next time the user attempts to open the book, or worse yet, reinstall it.

 The first solution is to save the value that determines the user access in an external file (it could be an .ini, .js. .as or perhaps an oddly named file), in an obscure place.  You wouldn't want the user to be aware of it, because deleting it would allow the book to be reinstalled.

 The second, better and more involved solution would be to build an online Access or SQL database of disallowed userIDs.  That would be a lot smaller list (hopefully) than allowed IDs.

 Your reader would 'activate' their book the first time they opened it.  

 Your ebook would check in online to see that it was legal to open on this user's pc.  If the user was not online, it would check a few more times before shutting down, and requesting an online activation.

After disabling an ebook, any time it is opened thereafter, it would check back again to see if the ID was still on the disabled list, and behave accordingly.

That way, you could enable and disable the ebooks at will.

I don't know it does exactly what you want, but I think it does something similar.

The [color=blue]HYPrLock[/color] Refund Disabling system now works with or without an online database. You choose which version you want to use. Once a customer requests a refund, your ebook is automatically and permanently closed. NEW Super Easy version.

Nice effects on the web site, but I have a suggestion.  Most web users use default settings on the browser, and your black text on a dark background makes it difficult to read.  

Take care,