Search results

Thank you for suggesting a solution. A. Microsoft proposes a macro either with Application.DisplayAlerts = false or with ThisWorkbook.saved = true to disable the message. I tested both of them. Although running properly they unfortunately do in fact not disable this particular message. B...

Suppose the filename of the source file is aaaa.xlsb, the filename of the padlock coded file is aaaa.exe and the filename of the according secure workbook is bbbb.xlsc. If I intend to close my coded workbook bbbb.xlsc, Excel comes up with the following question in a Microsoft Excel Frame: Do...

One of my customers has the following problem: After selecting choose save he gets a %SAVEFILENAME%-window with the following error message: %SAVEFILENAME% funktioniert nicht mehr. And he is unable to select and load any desired xlsc-files, except lastsave-files with his exe-file. (only the...

Supposed the exe is set to “Manufacturer-allocated Serial Number of the USB stick or first hard disk” according to your recommendation. Suppose the customer produces his System ID with his USB Stick plugged and gets its key according to this configuration. Does his System ID Change, if he later...

Ok, I will try the setting “Manufacturer-allocated Serial Number of the USB stick or first hard disk” instead of “hard disk serial number” with this one customer and report. Which means this customer needs a special version of the exe because I do not like to force all my other customers to ask...

As mentioned above, I always used hard disk serial number as system ID options

Yes I did. But they all have the same master key, the same GUID and the same Appl. Secret Key. I never changed these 3 items. Customers take the (same) exe from my dropbox, so they all have it identical within the same update period. Other customers and myself have no problem with opening the...

There are only too versions available for my customers. The 64Bit- and the 32Bit-Version. Should he start the wrong one, he gets a clear hint from the error message, that he needs a 32 Bit Version and has a 64Bit Version of Excel and vice versa. However my customer gets the message, that the key...

I used Use hard disk serial number

I have a number of customers who use my padlock-coded excel and the hardware-locked key I produced for them from their System ID has always worked fine. As Activation Settings I use: End users must enter an activation Key… Use hardware-locked keys… with System ID Application Master Key (unique)...

Ok, thank you. Now clear to me.

The 2019 Version of xlsPadlock allows applications to be translated into the language of my choice. From the user guide it is not clear to me how to achieve that. The advanced options allow to save workbook files against the language of vba. What does it mean?

True indeed! Thank you, problem solved!

Thank you. Because you first need to know… Either of the two situations may occur. Yes I use Applications.EnableEvents. It is set on false just before the command intended for saving with xlsc-save-dialog-box. Reason: to inhibit firing of the Public Sub Workbook_BeforeSave. No I do not use...

Unfortunately no success: I tried both the suggested 11.3 method as well as the 11.4 method (Suggest a filename for the save dialog box) from the Padlock Manual. Both of them I tried as a call from the Private Sub Workbook_BeforePrint (cancel As Boolean) as well as a call from an ordinary sub...

Thank you for investigating. Yes, I verified that (the uncoded) Excel allows saving once before print is fired using Private Sub Workbook_BeforePrint. However not with the command ThisWorkbook.Save (in the uncoded Excel this command does not initiate saveas and no dialog). The command (or set...

Yes, I confirm that Workbook_BeforePrint fires correctly.

I have a similar need as barcop101: I want to open the secure save dialog box via a macro to encourage my customer to save his xlsc. So I tried with ThisWorkbook.Save . Used in sub A this works fine. Put in an other sub B, this does not work. Sub B is the Private Sub Workbook_BeforePrint...

Did you release the updated version with an new filename? If no: How should the end user be able to distinguish between the two versions? If yes (recommended): Let the end user check the updated filename on top of the frame of his padlock-coded excel window frame.

I sent them to [email protected] on 24 August Here they are again. Please confirm reception. Reguards Hanspeter hpkpf