Schemes for runtime solution registration
I'm sure this has been discussed many times, but couldn't figure out a good search string to find it. I'd like to know what others here use for controlling registration of their shareware runtime solutions. You send a trialware version your runtime solution to someone. They pay you. What do you do next?
Right now, I can envision having an extra file called KeyFile.USR. It has a Name field, and accompanies your other runtime solution files.The trialware version is empty. The user is locked out of this file, so can't add text to that field. If the solution sees that field is empty, certain limitations are instituted in the database. If you send them a new KeyFile.USR, that has their name in that field, all features of the database are fully functional. That's what I imagine for now. What are others doing?