Hello
Would it be possible to design the unlock keys such that they can determine which features to unlock in a compiled XLSM file? In other words, by way of example, the unlock key (or components thereof) would be checked by the VBA and the OfficeRibbonX editor would be used to enable or disable icons on the ribbon to grant access to features.
Alternative workable suggestions welcomed.
Thanks
It’s difficult to upgrade the current licensing system to integrate more info into registration keys.
However, we added a way to retrieve custom info about licensing through the validation process. It’s explained in the documentation:
Would it be useful in your case?
It wasn’t quite what I was thinking but it has possibilities. Presumably I need to capture the right data at purchase time then pass that back into the exe to enable or disable certain ribbon items - which in turn will turn features on or off. I am trying to avoid separate builds with different features allowed. Am sure my developer will know if/how we can capture the data.
Thank you,
Dave
Could you make a 16 byte user data field that would append to the computer code if mandatory. It wouldn’t be part of the unlock key process unless non-blank. That would preserve previous keys and allow the user data field to contain optional items when we generate the keys. In our case, we don’t use the web to generate keys. (I’ve developed this before with generating activation keys … Contact me offline if you want more information)
Apologies for delay in responding. Am not sure. It would probably depend on whether the data field could be called by the Ribbon Callbacks to enable or disable the menu items (icons). Am looking at the practicalities of one build with functionality to switch on/of certain aspects at registration time versus separate builds or simply no restrictions. Therefore considering what options are available to me.
Thank you.
