Recent content by doughayman

OK, thanks. How much is the upgrade price? Will the upgrade still support Office 2000 Excel?

Version 1.4.0. I purchased it back on 6/16/2014.

Anyone ever see this? I built my .EXE on a Windows XP system, and it installs and runs fine on XP and Windows 7 systems. It installs fine on Windows 10 Pro System, but when invoked, it begins to run with my splash screen being displayed, but I ultimately get the following run-time error: “Could...

Yes, me as well. I looked for it for hours, and couldn’t find it, until I expanded the Functionality tab. Happened to me too, on my Windows XP system, but it is there, and works well.

Additionally, on my development Windows XP SP3 machine, I just XPSPadlock-compiled my spreadsheet under the auspices of Excel 2010 (recall above I did it with Excel 2000). Same registry error under the Standard User accounts. I also XPSPadlock-compiled my spreadsheet on my 32-bit Windows 7...

Hi, I just saw this option, tried it, and it works. This doesn’t mean though, that the .EXE and .LIC files can be copied to another machine and work, right? I have re-created the above run-time problem on 2 different Windows 7 machines; one 32-bit, and one 64-bit, with the identical error. One...

The latest & greatest… Version 1.3.3

An XLSPadlock-generated spreadsheet application that requires an Activation Code to enable the program on the target machine, will NOT run from within a Windows “Standard User” Account. After the application is invoked, the requisite Activation Code screen appears. Once the requisite Activation...

OK, this is NOT a Pacquet Builder issue; it is an XLSPadlock issue. I re-compiled my spreadsheet application with XLSPadlock, disabling the requirement for Activation Code. I built and installed package from within a Windows 7 “Standard User” account, and the package installed and application...

OK, I definitely isolated this problem to be a Permission issue. I created a “Standard” User account on a 32-bit Windows 7 machine, and installed my simple XLSPadlock-generated .EXE, in which I protected my worksheet. When I install, run, and provide Activation Code, I get the same registry...

I built a 64-bit app this morning, and ran it on the effected machine, and I get the same Registry Application error noted above. So, it has to be a privilege thing, I would imagine. Since Activation Code logic requires the ability to write to the Registry, what is the minimum User Account...

Further to above, I was able to get user/pass for this machine, and create an Administrator User Account. When I run the 32-bit app on this 64-bit OS from the Administrative account, I still get the above application error. This alludes to a 32-bit/64-bit incompatibility. Is there any remedy...

Hi, I have used Pacquet Builder 3.1.0 to build a 32-bit XLSPadlock-generated .EXE. I have built, installed, and run 32-bit generated application with Activation Code requirements on 32-bit Windows XP and 32-bit Windows 7 environments successfully, end to end. These machines ALL have...

Excellent! Have a nice weekend!

OK, thanks. I will need to play with this, and yes, I was planning to store the ApplicationMasterKey in a compiled CGI .exe that was resident on my server. Can I assume that we can make calls to your web API CGI program for production purposes, as a registered user of XLS Padlock? If your...