Recent content by StevegHI

Hello, Got the message again. Opened the IMFMain.exe compiled program, selected choose save file, and went to "Cancel" because I realized I wanted a recent file instead. Program ended immediately. Event viewer shows the following: Faulting application name: XLSPadlockLoad64.exe, version...

Hello from soon to be wet Hawaii! Just got the unexpected failure where the program exited without any obvious reason. It occurred when I moved the mouse quickly after the file dialog was displayed. Immediately went to the event viewer and got the following in the Application Log: Source...

I haven't forgotten. Watching for this problem. It's not easy to reproduce. I saw the criticism in a previous post. I take a somewhat different view. There are so many combinations of operating system features and third party extensions that anything any of us can do to help resolve this not...

I've gotten the same crash but it is intermittent, I don't use Nortons, and no client has reported it. Will attempt to reproduce, check event logs, and reply if I can find something substantive.

Just installed 2026.0 and had to uninstall previous version. Used the contact system and they simply had to clear it on their side. Kudos for the quick response!

Thanks. Apologies for the wrong forum. Minimum of 16 catches most inconsistencies real early. The build number is controlling, regardless of Excel release. For anybody's information, was able to get the minimum build level for various functions (attached). Obviously, sources not guaranteed

I updated my Excel spreadsheet to use "Let" and IFS". I just found out that "Let" requires a minimum of Excel 2024. I don't have a problem with setting the minimum but this level doesn't appear to exist in the information section of the Security, Excel Versions tab for compiling the spreadsheet...

Okay, got some excellent support from André C. from GDGSupport! ' Manual: 2025.2 Section 10.2.3 has some information on this particular call except for a different reason: 'Programmatically Hide Wait/Loading Dialogs 1. In the Workbook_BeforeSave: Disable [Call...

I'm on 2025.2 with Windows/10 and have a complex Excel spreadsheet. However, when I try to save, I need the option to cancel it in the Workbook.BeforeSave subroutine. Setting Cancel=True end exiting the subroutine doesn't cancel the save. It works in the xlsm version but not in the compiled...

Okay, tested it out on 2025.2. Did a A3=SetSecureWorkbookFilename(A1) where A1="H:\Xfer*.xlsc It appears to get the directory correct. The save screen looks like the following: It appears that I need to call the routine once with the directory name followed by a "\" and again with the file...

Thanks! Will check it out in about a week.

This is a cool procedure to ensure that expiration dates are not violated. If you want to make a one day expiration, don't use mScheduledTime = Now + TimeValue("24:00:00") . Consider changing it to: mScheduledTime = Now + 1 or mScheduledTime = Now + TimeValue("23:59:59") . We had this decades...

This problem has seemed to come back somehow. On 2025.1. The save dialog box still uses the previous save directory. Tried using SetSecureWorkbookFilename with both "F:\VBA Projects\Checkin_1.3\XLSPadlock_2025_1003\*.xlsc" and "F:\VBA Projects\Checkin_1.3\XLSPadlock_2025_1003\test.xlsc" It...

Has anybody else had this recently on executing an Excel spreadsheet compiled with 2025.1? When certain xlsc files are opened on Windows/10, the program simply ends without an error. Attempting to do the same thing on the Windows/11 Laptop, the file opens okay. There must be some dll that is...