Many years ago (FM 6) I built a system that once purchased, I would generate a license code based on a user name. I built a calculation that would take the user name and perform a routine to generate a code. When the user put in both their name and the code, the system would be unlocked. If the entered user name didn't generate the same license key as what I sent them (and was typed in) they remained in a demo mode.
Not the best way to do it as it didn't stop the user from using the same info on another computer or give it to somebody else. It also had the calculation in the schema - not optimal either. Doing something like this in a custom function might be a bit better. They didn't exist at the time I created my system.
For this runtime solution it was enough.
It depends on how and where you intend to verify the code.
If you are using lookup tables, ie, then a search for user name and the
licence type is will produce a found count, ie, a boolean value.
If you are using some sort of re-encoding scheme then your user name and
the licence type can be combined with a Luhn algorithm to produce a
If you should happen to go down the path of rolling your own registration code generator/validator, Todd Geist has a blog post on FileMaker and MD5 Hash that may be relevant to your endeavor:
I have not personally used the above yet -- I've only made a mental note about it, thinking it might be helpful for situations that require some kind of validation mechanism.
This is exactly the type of function I was looking for! I was afraid that I was going to have to resort to another plugin to do this.
While this type of key is certainly not super secure, it does provide a reasonable level protection from a customer enabling a feature they have not paid for.