Saving Without Using the XLS Padlock Dialog

Netspeedz

New member
What are the settings to allow a compiled Excel workbook to just open up without any XLS Padlock dialogs asking what workbook to open, etc? I've tried several different combinations of settings in XLS Padlock and apparently have not found the correct combination or the single setting that allows this. All I'm looking for is the compiled .exe to basically function just as an .xlsm would function - just open and allow the user to save modifications and then reopen without all the complicated dialog boxes flashing in their face.

Any assistance would be appreciated.

------------
 
Solution
Here are the options:
1741897490314.webp

Since you already started to make changes, you have to reset possible changes. Click "Delete Save Storage Folder", compile and try again.
Here are the options:
1741897490314.webp

Since you already started to make changes, you have to reset possible changes. Click "Delete Save Storage Folder", compile and try again.
 
Solution
That is exactly the settings I have currently. Tried it again with recommended 'Delete Save Storage Folder'. Same result. The .exe is not saving any modifications. The workbook itself saves perfectly.

------------
 
Strange indeed, I just tested it again and it works on our side. With the options above, you start the EXE, the workbook is opened, you make modifications to it and you can save them. You then close the workbook. Once you start the EXE again, the workbook with the previous changes is automatically loaded.
Do you also have these options?
1741904994786.webp
 
Ah - seems to be saving now. I believe the setting I was missing was the 'Do not allow loading/saving other workbooks (even with VBA code)'. I understood that setting to mean that a user could not have any other Excel document open when the .exe was open. I'm assuming this setting is referencing the workbook that was compiled to an .exe.

In any case, that issue is resolved. Still have another issue (Ticket 5766 - regarding how to disable selection of cells that are 'locked' in the original .xlsm).

Appreciate the quick responses on this. Was looking to get the issues I'm having resolved quickly as I need a utility that will convert current .xlsm applications.

------------
 
Great that it works for you now. For the ticket, our dedicated support tech should reply to you soon.
The saving of data in a compiled .exe has quit working with the paid version. The settings you provided worked with the trial version. I'm very disappointed. I really need saving function to work. What good is a spreadsheet if you can't save data?

------------
 
There is no reason why the paid version would work differently from the trial one, since it's the same code.
And of course data can still be saved. If you get troubles on your computer, maybe some incorrect setting, try resetting with the "Delete Save Storage Folder" button as shown on the screenshot above.
 
I actually already tried that and it didn't help. Not sure why, but it suddenly started to compile xlsm to .exe that could save. I'm a bit concerned about the inconsistent behavior. Will continue to test. Hoping I don't have to request a refund as I would like to continue to use XLS Padlock.
 
Really strange issue but great that it works for you too now (y).
Not sure if I should open another post but this should be an easy question. Is there a way to disable the log output when building an .exe? Also, what exactly is the difference between a template and the file created when saving on exit?
 
Is there a way to disable the log output when building an .exe?
No. Is there a reason why you don't want the log to be created?

Also, what exactly is the difference between a template and the file created when saving on exit?
The template contains less settings than the project file created automatically with "Save and Close". A template is used to share common settings between different projects.
 
No. Is there a reason why you don't want the log to be created?


The template contains less settings than the project file created automatically with "Save and Close". A template is used to share common settings between different projects.
This is a personal preference. The only time I want a log is when things are not performing as expected. At that time, I would enable logging. I just don't like all the extra files 'clogging' up things. There are many utility like applications that offer enable/disable of log files. Like I said, personal preference and I'm not necessarily looking for this feature to be added.

What are the various settings that are different between the .xplp and the template? Does XLS Padlock remember the last saved .xplp and load it when starting the Add-inn or is there a way to load that file (not the template) before compiling .xlsm to .exe?

Just curious - what does 'xplp' stand for?
 
OK thanks for the feedback!
What are the various settings that are different between the .xplp and the template?
Settings related to the output file such as the application output file.
Does XLS Padlock remember the last saved .xplp and load it when starting the Add-inn or is there a way to load that file (not the template) before compiling .xlsm to .exe?
XLS Padlock uses the name of the current Excel workbook file to determine the project file by just adding ".xplp" to the filename.

xplp = xls padlock project
 
Back
Top