Search results

@Josef P. : I have had this topic on my radar for a long time and am very interested in it. However, I haven't yet found the time to familiarize myself with it. But I am very grateful for your monologue ;)

Thanks a lot for this validated information, @isladogs , @sonic8 and the Access team! The only 'problem' is that it is estimated that only around a third of our customers use Access 365 (if at all), the rest use the still supported versions 2016 - 2024. Unfortunately, they cannot verify a...

The Microsoft Office Subject Interface Packages for Digitally Signing VBA Projects (https://www.microsoft.com/en-us/download/details.aspx?id=56617) sounded very interesting, but unfortunately it seems not to support Microsoft Access: SUPPORTED FILE FORMATS MSOSIP: Excel: .xla...

Thanks for sharing, Colin. The registry aspect could answer my question from #17: However, as I only have a valid certificate but no Access 365, I cannot test it.

For sure it doesn't work with Microsoft Access 2019 Pro Plus Version 2504 (Build 18730.20186), thats what I tested. Also not shown with my Access 2019. Regarding the time stamp: Time stamping shouldn't belong to the source of the certificate (file or token). But during the signing process an...

Thanks Colin, I will take a look on your site. As long as a timestamp was used at the time of signing, this should not be a problem. Do you know whether timestamps are set during the signing process using Microsoft Access? This is an important point that wasn't clear to me yet. I thought...

Thanks Colin for discussing it. (y) Perhaps the Microsoft Access team will also comment on this? Irrespective of this: Would you be so kind as to upload a signed ACCDB so that I can test with old Access versions whether the signature can withstand a “/decompile /compact”?

@The_Doc_Man : For me it is crucial to deliver decompiled versions of the ACCDBs, as we have had problems in the past with older versions of Microsoft Access correctly executing a database that was compiled with a newer version. Decompiling has always prevented this problem. Conversely...

Yes, please don't mention "I then tried the opposite and decompiled then compacted a signed project from the command line. The project remained signed!". :LOL: Just kidding. I hope this is by intention. I could live with it to decompile/compact after signing. Thanks for testing Colin, I...

My sequence is to execute “/decompile /compact” twice in a row. But that's not the point here. ;) I would like to know if it is still decompiled after signing.

Hello everyone, Unfortunately I don't have Microsoft Access 365, so I can't test it myself. But I am interested in whether a decompiled ACCDB is still decompiled after signing? Is there anything official to read about this, or official statements from Microsoft? Or is it possible to...

@sonic8 : As you're german too: There is also a german version of this article, having many comments maybe be interesing to be read too. ;)

I accidently read this very current article: https://borncity.com/win/2025/05/16/issues-with-visual-c-redistributable-and-odbc/ Maybe there is a relation to your problem with this library?

How about the regional settings in Windows? Maybe they differ from one computer to the other?

@Ranman256 : Which Version of Microsoft Access do you use and which update channel?

Thats what ChatGPT says about:

Or Microsoft SQL Server LocalDB.

That should not be the question. The question should be what it should do. See and follow Command Query Separation: So both, functions and subs, are procedures. Both can have parameters (which could be used for quasi return values if declared ByRef), but only functions can have a return value...

Thanks for testing @Josef P. and @arnelgp . So yes, finally the Object Browser 'documentation' is wrong. The online documentation doesn't mention a default value of the 'compare' parameter at all.

I have accidentally noticed a behavior of the String.Replace function that does not match the documentation from the Object Browser. According to the Object Browser, the default value of the optional parameter 'Compare' is 'vbBinaryCompare': However, the actual behavior is not like this...