Search results

You can of course use both of those operators in a query calculated field Anyway, I've just emailed the Access team as follows:

Happy to upload the old version of the file if that helps either of you.

There is no guarantee that MS will fix the issue with this very ancient file, especially when there is a newer version that works perfectly. The time needed to make these code changes is literally seconds. Personally I would recommend you just get on with making the changes needed especially...

I very much doubt MS will spend time fixing the issue with the older version but I may be wrong about that. Just make a copy and apply the changes. Test it then release. What’s the problem?

Why? You can do a simple find and replace on the entire project code. It will take no more than a few seconds to do.

Unless you use code as I assume @arnelgp has done, a form opened using acDialog will always have a title bar even if you remove the form caption and control box . . . no matter what the border style is specified as. Is your message form a 'special type' of form? In the screenshot shown in...

Presumably its crashing on the same line and also that using the newer OLEDB.12.0 code works. Even if MS do decide to fix it, I'd still change to the newer version throughout your code

I did say that ExifTool was command-line only back in post #11. I have no idea about a GUI for ExifTool. I'll reply to your direct message separately.

Just to say I have now reported the issue direct to the Access team (with a link back to this thread) so that they can decide whether its important enough to fix

It doesn't matter whether it’s ADO or ADOX. The main point is that you should be using Microsoft.ACE.OLEDB.12.0 with which there are no issues.

I took it very seriously and spent a lot of time testing both sets of code on 2 different machines. If the issue had affected the 'newer' OLEDB.12.0 provider as well, I would have reported it to the Access team as an issue needing attention. Anyone using A2007 or later should be using that...

Actually better than that - you can now remove the old Microsoft Jet and Replications Objects 2.6 Library as its no longer needed To run both sets of code I just needed these references: Suggest you mark this thread as solved.

@christian.dheureuse Thanks for picking up the ambiguities in my previous reply. As stated back in post #2, I do not have Windows 11 available I tested in 365 version 2509 build 19225.20000 32-bit and 64-bit with Windows 10 The version of msjtes40.dll is 4.0.9801.0 I may have forgotten to...

You’re welcome. As I mentioned, both articles describe a workaround which you can use.

Not a problem with either of my example apps.

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