Search results

Okay, that sounds plausible. The customer tells me they are upgrading their desktop environments to Windows 10 and Office 365 64-bit and this error message did show up. I will ask them if they have also upgraded other parts, such as their security software. Let’s assume that the customers...

Thanks for the suggestion. This might be a possible workaround. However, this feels I am doing one step back with XLSPadlock. Before, I used to create both 32-bit and 64-bit executables, which was more complicated and error prone. With a newer version of XLSPadlock this was not necessary...

One of our customers is encountering the following error message when starting our application protected by XLSPadlock. This is the first customer of several who reported this issue. Failed to prepare 64-bit mode. Error: System Error. Code: 203. The system could not find the environment option...

Strangly the missing dashes automatically added by the XLS Padlock manager do not seem to work. However, when adding them manually it does work (or something else has changed?). Anyway, problem is solved.

I have send this message on the contact form and to [email protected] to no avail, so I’m posting it here. I have renewed the software maintenance for XLS Padlock and according to the xlspadlock site I have now an active maintenance. However, I am unable to activate XLS Padlock v3.0.0...

I have tested XLSPadlock 3 and at first sight it seems to have solved this issue.

Is there any news on the expected release date of XLS Padlock 3, which hopefully contains a fix for this ‘Excel instance’ issue? I would like to communicate this to our customers, since they are waiting for a solution. Thanks in advance.

Good to hear! If XLSPadlock v3 is released, I will test it with a trial version. If it solves the issue, I will extend/reenable our expired software support for XLSPadlock, since we are stuck at v2.4. Please keep me in the loop.

I have tried the workaround by adding the suggested VBA to my workbook. It resulted in Excel not able to open any workbook anymore, with or without the protected workbook running. On opening of an Excel workbook (by an Excel file) it gives the error message [There was a problem sending the...

That sounds like a interesting attempt. Do you need a beta tester? I’m here to help. 🙂

Is it possible to extend XLSPadlock with the following behavior? If a secured workbook is loaded (with XLSPadlock), force each new workbook (from Desktop, Windows Explorer, by Start Menu, etc) to start automatically a new Excel instance?

For other people visiting this thread: "Save As" not working for non-protected workbooks XLS Padlock

That is indeed unfortunate and a limitation of XLSPadlock. Because of this, we might have to abandon XLSPadlock and move to a VB.net solution, although that will be quite some work and besides this I am satisfied with XLSPadlock. Are there any plans to improve this behavior somehow?

Unfortunately, enabling the setting “Do not allow loading/saving other workbooks” gives me the following error when I open an unprotected workbook afterwards. XLSPadlock-Do-no-load-error.PNG989×111 6.07 KB How can this be prevented?

I have tried the option “Do not allow loading/save other workbooks”, but it does not give the result I was hoping for. This is what happens now. Start the protected application ‘myapp.exe’ with the setting ’ Do not allow …'; Excel opens as expected. Open a new unprotected Excel from the Windows...

Hello, We are using XLS Padlock v2.4 to protect our VBA application. Recently a customer pointed out that Excel crashes after he opens a macro enabled workbook in combination with the protected XLS Padlock application. We have been able to pin it down and reproduce this by the following steps...

I have an application protected by XLS Padlock, which has an issue with the Excel save functionality. There are two scenarios with different behavior regarding the save functionality. Scenario 1 The user starts first the protected workbook/application, e.g. myexcelapp.exe The user starts...

v2.4 does seem to have resolved this issue. This topic/ticket can be closed.

Do you have any idea of the expected release date of XLSPadlock v2.4 with the fix above?

Since I have to release a new version of my application (due to the XLSPadlock bug), I am interested to know if the expected release date of v2.4 is still upcoming week. Do you have an update on the release date?