Re: [G.D.G. Software Forum] [XLS Padlock] XLS Padlock - Urgently - Help Please
Hello,
See EXE file in att. please !
Tell me the System ID and I will send you the activation code
Compare the results
gdgsupport Support
December 20Sure, we can test your EXE file. Send us the link by private mail.
Please, tell me when this bug will be resolved ?
My clients have difficulty with starting the program because of this function (ReadSystemID).
Hello, G.D.G. Software!
After update XLS Padlock 2017 my clients are faced with a new problem in exe-file.
A constantly appearing error window as indicated in the attaches.
And I’m a developer, also meet with the same problem in the following case:
when I compile the exe file, I can not continue to work on my PC with the original xls file, because it also produces such an error.
I must to open the VBA compiler and run the [Compile Code] function.
This problem appeared immediately after the upgrade to the XLS Padlock 2017
How to solve this problem ?!
We hope to release a new version in the very beginning of January.
Open the folder with your Excel workbook and locate the .xplcode file(s). Delete them.
Then reopen your Excel workbook, start XLS Padlock and recompile your project.
The “Stream read error” means that the .xplcode file got corrupted (somehow…)
This error occurs with clients while working with an EXE file!
What kind of .xplcode file can we talk about?
The problem occurs because the EXE is compiled with a corrupted version of that .xplcode file in your Excel workbook project. You can consider this .xplcode file as a cache that prevents XLS Padlock from compiling VBA code each time you compile the EXE. Delete the .xplcode file and rebuild your EXE file.
Hello !
When can I see the corrected version with the system ID function ?
You’ll get the usual announcement through our newsletter when the new version is out.
Hello !
Please, tell me when this bug will be resolved ?
My clients have difficulty with starting the program because of this function (ReadSystemID).
It’s been over a month now !!!
Sure, but we have got some other problems we must first solve. It’s normal development unfortunately it can take more time than initially expected.
Perhaps more simple tasks can be solved while working on more complex tasks. I usually do this during application development.
We meant problems in the current build of XLS Padlock.
Problem fixed in XLS Padlock 2018. Please upgrade.
Ok.
I will test it
I just installed version 2018.1 and get an error in all the functions called. I’ve recompiled a hundred times already and do not understand what the problem might be. In the previous version of 2018 everything worked without problems
When you compile your VBA code inside the VBA compiler, do you get an error? Try to change param1 defined as string to variant for instance.
When compiling - no errors!
What you are offering is not necessary!
I will have to redo all points of calling procedures and functions.
I had to remove version 8.1 and I work with 8.0 until you find out the reasons.
I’m constantly programming and can not jump from version to version.
Anyway, that’s probably the reason of your problem.
In the compiled VBA code (in VBA compiler), don’t use types for params.
For instance:
Function test(param1)
and not
Function test(param1 As String)
Why did this problem only occur in 2018.1?
I have more than 7000 lines of code and it is not acceptable in every version to make such global changes
