Search results

Attachments are in Dropbox: https://www.dropbox.com/sh/rvmjpgwk2geu7oy/AAA2HS-Ds33VRQTfXKNv9iW9a?dl=0

Hello, Okay I think I’ve isolated the problem. The analysis is attached. Also attached a PDF of one of the functions on the spreadsheet. I doubt I’d get a different result with the 2022 compile but will be testing it in a couple of days. Conclusion: Excel 2013 will not open a worksheet with...

I ran into the same problem with XLSPadlock 2021.1 on a Windows/11 with Excel365 and , “Excel is required in order to run this application. Cannot continue.” The .exe file ran successfully from a memory stick as well as a network drive. The .exe failed when it was run from both a root folder...

I’m running into the same problem. It makes no difference whether I check or uncheck that box. Windows/10 with Office 2013. Getting desperate for a way for this to work.

Okay, when is it coming out? Had to go through some real hoops to ensure I could save the .xlsc in the same path as the .exe file.

Could we include the custom information when we generate the activation key from the desktop? That would also be so helpful. It opens the door to an infinite number of feature codes and would allow additional security protection against unauthorized use on the same laptop. Steve Glanstein +1...

Correct. Just copied the file so she could use it. Steve Glanstein (cell phone)

Hello, Spoke with my daughter again. Here’s a better chronology: Failure message on .exe Closed a bunch of windows. Same failure message Closed all and rebooted Same failure message Connected to internet (considering possible problem with Office 265 verification?) Same failure message...

Thesis for teaching out to me. Only one computer. We have hardware locking. The key was set to expire at the end of June. It was my daughter’s computer and we haven’t distributed it yet. We’re still in a development phase but needed to use it to help a client on a last minute basis. She had...

Any chance of allowing us to provide and retrieve text (such as a licensee name or feature code) as part of the validation?

We just had an exe fail on Windows 11 with Excel 365…2 hours before a critical annual meeting! It worked yesterday and all we did was compile and provide a signature. Couldn’t use the .exe module. Any ideas? Followup … worked the morning after. No idea why?

I’m getting the same problem. I get a success and then an immediate failure: [5/22/2022 10:36:55 PM] GSignCode 2.1 – simple code signing utility [5/22/2022 10:36:55 PM] Copyright G.D.G. Software 2011-2016. All rights reserved. [5/22/2022 10:36:55 PM] [5/22/2022 10:36:55 PM] Certificate Subject...

Strange … no dat file in that directory. Steve Glanstein +1 (808) 423-6766 [email protected] Notice: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is...

Tried it with and without the checkbox. It still goes to a much older version of the application (Checkin_1.1). I’m at my wits end to determine where this reference to Checkin)_1.1 comes from (My software is now in Checkin_1.2).

Anybody have a work-around? Starting to distribute .exe file.

I have a similar problem. Previously posted as" Save during execution defaults to old directory". Don’t want to disable the save; just want to make sure it stays in the same path as the spreadsheet.

Unticked the "Store .DAT, license and save files in the same folder as the EXE file. Clicked on “Ex[;lore Save Storage Folder.” Received the following:

I have the Advanced option already set to save in the same folder as the EXE file (below). When I click on “Explore Save Storage” button, it shows the correct folder. Not sure why the Advanced option doesn’t seem to work.

Challenge A: Start process to create .exe Erroneously select both Save options, i.e. “Always show the ‘Load previous changes’ welcome screen” and “Save changes automatically and load them without prompt next time”. After compile, try to open .exe file. Get the following: Click “OK” and it...