Search results

To work around the poor performance issue of arrays calculation as mentioned in my earlier post, I’ve developed my own compiled DLL for the main calculation engine in VB6 in stead of moving the code into the XLS Padlock compiler. I’m aware that my spreadsheet and the DLL could be stripped off...

Hi there, Is there any progress regarding this issue? Is it possible to know the time frame for this?

Is it possible to add Yubikey or a generic FIDO U2F Security Key as additional option for protection with hard keys? Protection with USB stick is not good enough since these sticks are easily to be cloned. Going with Enky SL dongle only is not really a good business decision since we hardly get...

Thanks for that, but it isn’t really what I’m after. What I’m looking for is the remaining days (or expiration date) of the official/registered compiled workbook (NOT TRIAL) which is activated by a key with expiration date. Hope that I can get my point through.

I want to show the expiration date and number of days left in order to remind customers to renew their subscription before it is expired. How can I use VBA to retrieve the expiration date from the activated licence?

Thanks for your transparent explanation. Highly appreciate it.

Hi XLS Padlock team, I would like to have the following features available in the future version of XLS Padlock: A CANCEL button in the opening dialog box to allow me to cancel opening the workbook. It would be helpful especially when we just accidentally click on the EXE file and we don’t...

That’s a good news. A big thank for that. My apologies for the misleading information regarding the 253 characters passwords length mentioned in my earlier post. There was no error when compiling to EXE, but they did NOT work for me when I tried to run the compiled EXE file. An error message...

The macro didn’t make it to the MsgBox. It crashed at the GetLasRow function as shown in the below screenshot

I didn’t send the error report for some reasons. I like the additional security feature by protecting the workbook by password as mentioned in the Section 5.2.6.2 of the user manual. I expected that the provided password is encrypted and safely stored within the compiled exe file, and I hope...

Thanks for your effort trying to reproduce the problem. Looking forward to having the solution as soon as you can.

The compiling error for xlUp is gone. But I couldn’t get the function to work yet though there is no compiling error. What am I missing here? Below are the full code that I put into the compiler. Function GetLastRow(ByVal i As Long, ByRef sh As Worksheet) As Long ’ Given Column number...

Thank you. It works now.

No, I didn’t password protect my workbook. And yes, I was asked to send an error report.

I’m using the V3.0.0 at this moment. Big thanks to the XLS Padlock team for their great effort to release this version. I put randomised-customised passwords of 256 characters in length into Workbook Password/ Application Secret Key/Application Secret ID/Application Master Key/ Application...

I successfully brought my main function which contains more than 2500 lines of codes into the VBA Compiler. It was able to run eventually and produce similar results compared to what the original VBA codes did. Yay!!! However, there is an issue - code performance. The compiled code is really...

I’ve found the culprit for the error. The use of DIM for VarArrayCreate makes this var local. I removed that DIM and it works. The full code is below. Public XS2RunList as Variant Public nXS as long Sub XS2Run Dim i as long XS2RunList = VarArrayCreate([1, nXS],12) For i = 1 to nXS XS2RunList...

I got two errors: Cannot create file “C:\TEST\test1.xlsc”. The process cannot access the file because it is being used by another process GXLSPlock error: the add-in has fired an exception. Cannot create file “C:\TEST\test1.xlsc”. The process cannot access the file because it is being used by...

I got the following error msg when compiling the code. Unknown identifier or variable is not declared: ‘xlUp’. Source position: 282,51

I was thrown an error when trying to recall the value stored in an array, see code below. What am I missing here? Public XS2RunList as Variant Public nXS as long Sub XS2Run Dim i as long Dim XS2RunList = VarArrayCreate([1, nXS],12) For i = 1 to nXS XS2RunList = i Next Msgbox (XS2RunList[1])...