Search results

I recently updated windows to 24H2 and my Paquet Builder 2021 in 64 bit version showed a mainscript error and does not work anymore. I reverted back to the 32 bit version, so I can work. Just wanted to flag this. I am not sure that it is windows update related but as it always worked without any...

Is there a way to hide/disable the Protect/Unprotect Workbook in an executable. It is possible for Worksheets. Thanks

I did create an .exe file of my excel sheet. It appears that I can run multiple sessions of this file on my computer. How is this possible ? As I intend to allow only single user access, this would not seem possible if the exe would be activated on a server and various user could work at once...

When trying to include a code signing certificate in a compiled excel sheet I do get an error and the certificate is not being included. I have tried all possibilities of formats and so on without any success. When using the same certificate with your Pacquet Builder it works without any...

I did just get the info from a new client that is using excel 2013 that instead of 1 instance, 2 instances are opened of the workbook. However one instance seems to be empty and the other one does have the workbook. The strange thing on top of that is that the “empty” instance can however show a...

I have just installed 2.1.1 and have run into problems with protecting vba code. I am using excel 2010 for compiling and testing on excel 2007 the exe. Selected options I did set a password for the VBA project in my vba developer window. I did NOT select “lock VBA project” in XLSPAD I DID...

When trying to install 2.1 on my computer (32 bit / Windows 8.1) I do get an error message / request to show the path to a file called lspadlocksetup.msi for removing the older 2.0 version. I cannot locate this file and thus cannot install 2.1. What do I need to do ?

I am using the workbook after save procedure to calculate a table after the workbook has been saved. In a compiled file this procedure is not anymore active. The _BeforeSave procedure is being called but the _AfterSave procedure not. Any ideas why this is happening and are there any workarounds ?

I have compiled a workbook in 2.0 version without using VBA lock and without hiding the VBA editor and cannot see the developer ribbon anymore. I cannot access excel options (greyed out) and I cannot go the route via right mouse click button on the sheetname “show code”. How can I allow any...

I have compiled a 30MB excel workbook and when saving a variant via the secure saving option the time for saving the file takes ages compared to the un-compiled file. In order to try to reduce this time I have hidden all the cells that are unnecessary to see for the final client and I have...

I have a binary excel file that does run a macro on the “worksheet open” event copying a range of cells for a few thousend times and eliminating those rows at the “before worksheet save” event (in order to keep the saved file small). When I compiled this file without the XLSPAD generated...

You mention in your product guide line that it is possible to create a 64 bit executable specifically for clients that are using a 64 bit version of Microsoft Office. On my computer - with a 32 bit hardware, 32 bit windows 8.1 and office version - this option is greyed out and not accessible...

I am using a complex workbook that at some point in time must export data from the protected file into a new to be created excel file. I have written vba procedures for that. When executing the vba procedures I do get after the export of the files the “standard xlspadlock” window to save the...

I am using version 1.4 and do want to use the simple VBA Lock feature. In my non encrypted file I did not use a vba password and with the simple VBA Lock feature I did expect that in the protected file my vba project would not be visible as metioned in the release notes. However the VB Editor...

Hi, 2 Questions: I do have a spreadsheet with a very significant amount of formulas (a few hundred) that I would like to hide. The workbook does however exist out of a few million cells that are all dependent on iterative solutions of those formula cells. After hiding about 50 formula cells...