Search results

Sure, here is an article that should help you: https://www.vbapadlock.com/blog/vba-padlock-vs-xls-padlock-which-one-do-i-need

Thanks for the clarification. The IsTrial() function is intended to work only when the workbook is running inside the compiled XLS Padlock application, not while testing the original workbook directly in Excel. So in your original workbook, this line: Set XLSPadlock =...

The XLS Padlock free trial is fully functional, allowing you to test it for as long as you need.

Yes — this is absolutely possible and it’s a very common licensing pattern for XLS Padlock applications. The concept is simple: the application starts normally, then VBA checks whether the app is running in trial mode. If it is, a dialog prompts the user to either continue the trial or activate...

The error shown in your screenshot indicates that SignTool.exe cannot be found on your system: This happens because the Microsoft SignTool utility, which is required to digitally sign the EXE file when using the SignTool Commands method, is not installed or its path has not been configured in...

VBA Padlock 2026.1 is here! We're excited to announce the release of VBA Padlock 2026.1 — an update focused on making it easier to compile real-world VBA projects with minimal or no modifications. This release brings Enum support, full error handling, array operations, pattern matching, Unicode...

Answered to your ticket.

The "Invalid code page" error is related to your client's Windows regional/locale settings, not to the Office version itself. This explains why it works on your machines but fails on theirs. The internal spreadsheet engine of XLS Padlock expects certain regional settings (particularly the code...

We'll launch next week our new product and we also got news from the third-party provider for your problem in ExeOutput, so we'll have news next week. Sorry for the delay!

Thank you for the detailed log — that's very helpful. The error code 0x800B010A means "A certificate chain could not be built to a trusted root authority." This is not an issue with XLS Padlock itself, but rather with how Windows is currently validating your certificate chain. The fact that you...

It's a known issue that is going to be fixed in the incoming update. Thanks for the report!

No new updates for now, as other incoming projects have caused some delays. We're still working, thank you for your patience!

Thank you for providing the full compilation log. The issue is not related to your HTML content. Your compilation progresses correctly until the very last step, where HTML Executable attempts to generate its internal build file (.hek). The fatal errors you see are caused by Windows permission...

This error indicates that your antivirus probably blocked the creation of the temporary EXE file. Are you using an antivirus software?

All texts can be localized using the corresponding tab: More info here: https://www.htmlexe.com/help/topics/localization.html

You can modify the HTML source code for this dialog box in HTML Executable under System HTML Pages. From there, you can change the title however you prefer.

There is a bug confirmed in this section that we will fix in next update. Remove the 0= For instance, the following instructions work: [SignToolCmd] sign /v /d test /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /sha1 HASHSTRING /sm {$PBOUTPUTFILE$}

What steps did you follow? If you select jsign as the signtool in the Environment Options, PB will use it. You can then choose your custom commands.

Sorry for the delay. We are still working on the issue, and we hope to have an update next week.

What you are missing is indeed the built-in Web Update mechanism of XLS Padlock. Simply increasing the version number (for example, from 1.0 to 1.1) is necessary. Then, you can configure your application to automatically check for updates at startup or add a “Check for Updates” button to the...