Search results

I've now done some more testing in both 32-bit & 64.bit Access 365 32-bit The code works using OLEDB.4.0 with both .mdb and .accdb files. In both cases, it fails with OLEDB.12.0 64-bit Both sets of code fail with both .mdb and .accdb destination files I agree with @tvanstiphout that this is...

Thanks @christian.dheureuse and welcome to AWF I've tried your code with both OLEDB.4.0 and 12.0 using A365 v2509 19225.20000 64-bit but still get error 3706 on the Provider line I'm reluctant to spend time reinstalling the drivers for 64-bit as the 2016 Redist no longer seems to be available...

REMINDER: The next Access Europe User Group meeting will be TOMORROW (Wednesday 3 Sept 2025) starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). The session will led by Adam Waller For more details, see post #1

Hi @bignose2 This bug was first reported by Mike Wolfe on 29 Aug with details passed on to the Access team the same day https://nolongerset.com/bug-assertion-failed-regexp/ I included it in my article summarizing all known bugs for July/August...

I have a couple of example databases showing the idea explained in post #3: https://www.isladogs.co.uk/highlight-current-record-transparency/index.html https://www.isladogs.co.uk/highlight-current-control-transparency/index.html

Unfortunately some issues appear to affect a limited number of machines. I have two different long standing bugs that others can’t replicate. I’ll watch out for other reports in case it is a broader issue than it currently appears to be

I wasn't . . . but I am waiting on the OP 😉

@CJ_London Just to confirm that I've had a response from a fellow MVP (Karl) who tested in a Hyper-V VM with W11, A365, 64 bit, latest CC build. This provides further confirmation of my belief that that there isn't a general issue affecting Win 11 users.

I'm about to ask another fellow MVP to test under Win 11 and if it is confirmed then one of us will report it. Before I do so, please will you answer my questions from post #2

I don’t see why you can’t use DAO or DDL just for this one section of code even if you continue to use ADOX elsewhere. Also try OLEDB.12.0 as already suggested in post #2

I installed all the references to try using A365 under Win10. However I get a class not registered error on the provider code line. I suspect this is due to having 64-bit Access and the drivers may still be 32-bit? My memory of ADOX is that it is far less stable than either DAO or DDL

I don't have Windows11 to test your code against but some questions 1. If you disable those two lines, does the rest of the code complete without error? 2. Does it work if you change to OLEDB.12.0? 3. Have you tried using other CreateTableADOX code e.g...

That’s also my solution

Not allowing Nulls with Boolean fields was arguably one of the biggest design mistakes that the Access team made way back with version 1 in 1992. This issue can lead to write conflict errors with data from other RDBMS such as SQL Server. Unfortunately, structural decisions such as that will...

@June7 Not sure what you are referring to: GMail and Outlook email accounts or the two applications? The whole point of CDO is that there is no need to make use of external email applications. Having said that, I do have code to use CDO with Outlook for those who prefer to use it as an...

Before you do that, suggest you at least try using CDO to send email. CDO is easy to setup and won't be affected when MS eventually discontinues Classic Outlook in a few years time

Neither the web version of Outlook nor the desktop New Outlook can be automated. Your choices are to use the classic desktop Outlook or bypass Outlook and use CDO from Access or possibly the badly named Graph API

If you have that many files to review then I'd consider using ExifTool

The article mentioned in post#15 has a link to another article with the explanation

Sorry I must have just assumed you were on Win10. Actually I think that may have helped confirm this isn’t a general bug related to Win 11 but may be specific to certain workstations only. I’ve asked several other colleagues to check in Win 11 as well.