Yes, once again (I know I’m sounding like a broken record – not my fault, speak to Microsoft!), Patch Tuesday has gone and messed up the jet dll (msjet40.dll).
Some of the symptoms include:
Impacted system are those still using Jet, so any of the older mdb, mde style database.
Just a very quick post to advise everyone that Update 2005 12827.20268 (released June 2, 2020) appears to be causing various problems with Decimal fields in Microsoft Access databases. (I’ve seen reports of other issues, but those remain to be confirmed)
Right now, I’d recommend steering clear of the update altogether and if you’ve been impacted by it then you’ll need to uninstall the most recent update, refer to Microsoft Office 365 – Uninstall an Update and revert your office installation back to a prior build. Don’t forget to block further Office Automatic Updates once you revert your build or you will be back in the same position within a few hours.
Another suggestion by fellow MVP Alumni Tom Wickerath is, if you truly don’t need a Decimal field, perhaps the easiest solution would be switching to Single, Double or Currency as this current bug only impact Decimals.
There’s yet another bug, dating back to at least February 13th by the looks of things, causing headaches to a select group of Access user and the symptom is that the lock file (ldb/laccdb) does not go away after the database or connection to the database is closed.
All I can say is that the Access Dev Team were made aware of the issue and we are told that a fix should be coming soon. Fingers crossed.
It’s that time of the month, patch Tuesday, where Microsoft is supposed to resolve problems, but most often seems to ends up causing new ones at the same time!
Case and point, the latest Office update which has broken Access’ ability to recognize SQL Server Identity columns!
Firstly, it is important to note that this new issue only impacts those that use SQL Server as a back-end for the applications.
Furthermore, it only affects new links. So existing links should continue to work properly, but if you create new one, or Refresh existing links, then this issue will appear and impact you.
The problem can manifest itself in a number of ways and can impact forms, code, … You may suddenly see #Deleted in your tables/queries, you may be now getting error 3167 – Record is Deleted, …
The issue was introduced in Office update/version 1912.
Well it would seem Microsoft has, yet again, let another MAJOR bug slip through its net causing widespread mayhem of the Access world!
This latest bug impacts all flavors of Access 2010+ regardless of bitness, installation type (MSI vs CTR, …), …. so Access 2010, 2013, 2016, 2019, Office365, including the Microsoft Store edition of Access, are all impacted by this latest issue regardless of file format. (Yes, now is the time to panic!)
If your database suddenly started report an
Error 3340 – Query ‘Your Query Name’ is corrupt.
then read on!
I thought I’d pass along a bug brought to my attention by ‘Jason’ regarding an issue with using the Int() function.
Now there has always been an issue with calculations due to floating point issues, which I’m not going to even attempt to get into in this post. There are far greater minds that have elaborated on this subject in the past. That said, whenever you need to perform any sort of calculation, you are best to always use currency or decimal data types.
Back to today’s post, the issue with the Int() function. Int() is used to return the whole number part from a number. So,
? Int(1) 1 ? Int(5.25) 5 ? Int(13.65) 13
In a query
SELECT 40*0.3 AS Expr1, Int(12) AS Expr2, Int(40*0.3) AS Expr3;
Results in
12 | 12 | 12
=INT(40*0.3)
Results in
12
Not to be confused with the Access – Bug – Database is in an Unrecognized Format, KB4480960 released January 8th, 2018 breaks Access ’97 resulting in an “Unrecognized Database Format” error.
There are reports popping up in various forums
Incompatible Microsoft Access 97 and Windows 10 January 2019 Update
Access MVP Alum Scott Diamond just reported that version 1811 Build 11029.20079 apparently breaks Microsoft’s MAPI implementation. From the report, you simply receive the generic “Microsoft Access has stopped working …” error, so not much help there.
So if you built any e-mailing procedures around it or use libraries such as vbMapi or Redemption do not update or you’ll get a nasty surprise!!! If you have already updated and are facing this issue, then seriously consider reverting your installation back to a prior build, see Microsoft Office 365 – Uninstall an Update.
A quick post today to regarding a bug I’ve seen reported a few times (one thread is provided below as an example) in which a database runs fine as an accdb file, but once converted to accde the VBA will not run.
Obviously, the first thing required is to ensure the front-end file has a Trusted Location defined, but in this case, that is already done, yet the VBA code still would not run. As it turns out, the solution was to do some VBA spring cleaning and delete any and all empty procedures.
Stuff like
Private Sub Form_Load()
End Sub
needs to be purged.
So if you have any procedures you started, but never added content to, delete them all. Once your project is purged of such procedures, create a new accde and try again, it should run smoothly.
Hopefully this will help someone figure out why things aren’t working.
Yep, another update, so another bug has surfaced, this time with sending e-mails with database objects in which Access reports
Microsoft Access can’t open the mail session.
and this appears to occur in 1807, although the official Microsoft page states 1806 and later, running on Windows 7 PCs, although I have seen reports of people claiming to have the issue on Win10.
Continue reading