Recent content by AHeyne

Perhaps you could encourage the creator of the files in the source folder to include the hash of the files in the file name when creating or modifying files. Then you wouldn't need to calculate the hash of the files in the source folder every time, but could take it from the file name.

Just because you didn't mention it (I'm not sure if you are aware of it): The reason why your forms seem to large on the laptop having the same screen resolution for sure is a different scaling factor in Windows screen settings.

Since I have had different experiences and cannot agree with your statement, I did a little research. The crux of the matter when using ADODB in conjunction with, for example, "RecordCount" is which version of the ADODB library you have referenced. In my 64-bit VBA environment: - "Microsoft...

While we are on the subject of what needs to be considered when converting 32-bit code to 64-bit, it is also worth mentioning non-API-specific issues: In an "ADODB.Recordset" object, the "RecordCount" property has the type "Long" in 32-bit and "LongLong" in 64-bit. So if the number of records...

One theory I have as to why @arnelgp already has "VBA.RegExp" in his Office-LTSC is that he also has Microsoft Project Professional 2024 installed (which is not an LTSC version). Perhaps the new VBA version/environment was installed on his computer via a Microsoft Project update?

Okay, it looks like there is only one channel for each of them: “PerpetualVL2021” and “PerpetualVL2024.” In any case, I can't change the channel in the UI.

Here is a small addendum from me, as I now also had access to two Microsoft Office versions that have already been mentioned here: 1. Microsoft Office LTSC Professional Plus 2021 Version 2108 (Build 14334.20296 C2R) 64-bit 2. Microsoft Office LTSC Professional Plus 2024 Version 2408 (Build...

@MarkK : It simply could be a "WScript.Shell" object. CreateObject("WScript.Shell") @pdanes : In such weird situations I always try to DEcompile the accdb. Edit: @RonPaii : Yes, it seems he has. He wrote:

The difference in behavior could be a matter of responsibility: Microsoft Access Team vs. VBA Team

Ok, the problem seems to belong to my location: But it's no problem. It's not that important.

(Currently?) the link doesn't work...

If the storage of an image as an Ole object stores just the raw binary data (I'm not sure) then storing a Base64 string instead would need more storage: (see here)

I could test another one, exactly the same version as @theDBguy has: Microsoft Office Professional Plus 2016 Version 2508 (Build 19127.20222) One more information from my side: It is a 32-bit Access. 'RegExp' is available in 'VBA'.

Base64 can also be represented as a character string.

@CJ_London : Good point. The versions I mentioned are both 64-bit.