Hi,
I am trying to lock a total of 12 spreadsheets in one .Exe file only .
Where when they get the access by license ,they can browse them all with one license only.
I did add them in the companion files area,but it seems useful only for linking cells.
Otherwise i need to create 12 different .Exe and licenses every time,wich is wild to manage !
It seems you’re facing challenges with managing multiple licenses for your spreadsheets. Managing 12 separate licenses can indeed be complicated. However, there is a way to simplify this process.
Instead of creating 12 different .exe files with separate licenses, you can configure all 12 executables to share the same licensing information. By doing this, once a user activates one executable, the other 11 will recognize the activated license and function as if they have been activated as well.
To achieve this, you need to ensure that the following parameters are shared across all 12 projects:
By using the same Application GUID and Master Key across all the executables, they will share the same licensing information, allowing for a single license to unlock all 12 spreadsheets.
Please can you kindly a step by step answer,
It can be useful then for everyone to use,as the user guide it has no citation about this ,
I’ve applied the same GUID and Main app master key from the main spreadsheet to all the other ones i want to include.
When i pack the .Exe only the main spreadsheet loads .
So i need to create an .exe for all the others too and the one license generated by the main one will work for them all right ?
If you don’t want to make a menu in your main workbook to open other compiled workbook files with VBA, then yes, you’ll have to make an .exe for each workbook file. Sharing the parameters as explained above.
You can also easily share parameters by using the XLS Padlock’s template functions in the menu:
Make a menu what does it mean.
A Macro that once clicked it opens the wanted spreadsheet ?
Will it be allowed by Padlock ?
Also if yes, what are the requirements.
do they need to be in the same folder ?
They have to be compiled too as .exe ?
We don’t know this software and guides are not provided for some aspects so it’s obvious that we lack on coming out with ideas in a closed environment software .
Please mate be helpful,You don’t cite any further detail to guide the user