Category Archives: MS Access Bugs

Access – Bug – .Fields Not Working Anymore

Reporting bugs will become my full-time job thanks to Microsoft!

The Problem

So there are new reports that version 2206 also breaks iterating over .Fields,

The gist of it being that it no longer returns .Field2, but rather .Field3 object breaking existing code.

You can read for yourself all the details by reviewing the Stack Overflow thread on the subject:

Access with breaking changes on Version 2206 (Recordset2.Fields returns DAO.Field3 instead of DAO.Field2) - Error 13

It looks like Microsoft introduced a breaking change with version 2206! 🙁
If you had code like
Dim rs as DAO.Recordset2
Dim fld as DAO.Field2 For Each fld in rs.Fields ’<- Code will break ...

I notified Microsoft about the issue, as have other MVPs I believe.

Microsoft has since confirmed the issue and suggested:

The simplest workaround for now is to change declarations of type DAO.Field2 to DAO.Field

Continue reading →

Access – Bug – Report Borders Not Showing

Yep, one more to add to the long list Microsoft Access bugs!

The Problem

As reported:

Access 365 v2206 (15330.20196) report formatting regression

Updated this morning, ZERO notes about Access updates so I figured I was safe: Went to generate a report... group header usually looks something like: Now looks something like: Confirmed a rollback to 2205 (15225.20288) fixes it. I’m not doing anything weird or zany with the border...

We seem to have a new bug that has surfaced in version 2206 (build 15330.20196) in which reports don’t seem to be properly rendering.

Fixed

Microsoft has supposedly fixed the issue by flipping flags at their end. So you need not do anything beyond close and restart Access.

Yes, it’s like magic. Microsoft can remotely alter your installation without your knowledge or consent.

Continue reading →

Access – Build 15225.20288 Causing Attachment Problems!

It wouldn’t be a Microsoft update without a new Access bug! OMG.

The Bug

As reported:

Attachment Field crashes after Microsoft Office Update

Hello everyone! At my work, we recently has an update from Microsoft Office and now we can’t use attachment field at all. All the access database would crash whenever we try to attach or remove attachment. Does anyone has similar issue? If you do, have you find any solution or workaround for...

and now confirmed by fellow MVPs, build 15225.20288 breaks attachment fields causing Access to outright crash.

Continue reading →

Access Hyperlink SubAddress Bug?

This is still in the very early stages, but it is looking like there is a new bug that has recently surfaced impacting Hyperlink SubAddress.

Threads such as the following have started popping up:

Microsoft Access (Version 2205) breaks Hyperlink.SubAddress following on forms

Microsoft Access (Version 2205) 32-bit breaks the following of the Hyperlink SubAddress property for controls on forms. To replicate the issue, on a form in Design View, add a Label control with some text like "Click Me". In the Hyperlink SubAddress property for that control, click "..." and then select another database object like another form. In Form view, click the label control "Click me", and the database should open the form that the property points to. This behavior works correctly in all Access versions prior to 2204, but in version 2205 the click is ignored.

Hyperlink SubAddress

The hyperlink subaddress in all my databases has stopped working! Help!!

Macros no longer working on hyperlink subaddress event | Experts Exchange

Macros being run from the hyperlink subaddress event of a button are no longer

so be forewarned that it is suspected to be a bug with 2205 so try and rollback your installation to 2204 or earlier.

As always, I’ll update this post should I learn anything new on the subject.

Continue reading →

Latest Office Update – Version 2204 Source of New Bugs?

My spidey-sense is tingling! (and not in a good way)

Access MVP Alum Gina Whipp has reported a series of issues with Access version 2204

• Property not found
• No current record.
• The search key was not found in any record.
• The object doesn’t contain the Automation object ‘YourControlName’ (And while that is control on the Form it is not used in the code anywhere. Oh, and yes that is the way it is spelled in the message but not on the Form.)

Continue reading →

Cannot Compact And Repair Access Database – File Already In Use

After the File Lock bug, we have now seen many reports of people no longer able to Compact and Repair their databases and are receiving error messages such as:

Could not use [filename] file already in useMicrosoft Access

Here is a small sampling of the various forum threads on the subject:

MS Access will not Compact and Repair on c: or d: drive

I've recently upgraded to Windows 11 and just noticed that no MS Access database will compact and repair.

Microsoft Access is not allowing me to compact and repair. Keeps saying its open etc

Microsoft Access is not allowing me to compact and repair the database. It keeps saying file is open.

Microsoft Access 2019 "Could not use [filename] file already in use" - just on Compact/Repair

I have been using the product for a while, but started getting the error "Could not use [filename] file already in use" when I try to Compact/Repair a database

Cannot compact database

I have Access 2019 and I am unable to compact databases. I get the error message: "Could not use [filename]; file already in use." This began a few weeks ago and I've been working around it.

Can’t compact and repair | Experts Exchange

Every time I try to Compact and Repair for the past week or so, I get "Could not use "blah, blah, blah.accdb; file already in use.

and many, many more.

Continue reading →

Cannot open any more databases – Another Access Bug

It’s turning out to be a rough New Year for Microsoft Access as we appear to be hit with another bug which has a number of possible symptoms:

Error 3014: “Can’t Open Any More Tables”
Error 3048: “Cannot open any more databases”
Error 3211: “The database engine could not lock table ‘TableName’ because it is already in use by another person or process” (unconfirmed)
Even after closing, the access process, msaccess.exe, remains and the lock file, laccdb, remains as well
Error “Already in use by Admin”

I’ve seen reports that the issue relates to build 16.0.14827.20158, but i”m not sure if it is limited to just that one build or not.

Fixed - 2022-02-08

It has been reported that Version 2201, Build 14827.20192, was release late last night or early this morning and fixes the issue. Verifying the build’s release note, it does indeed confirm this is a fix.

So you may wish to try updating your Office/Access installation and the problem should resolve itself.

Threads On The Subject

As they say, misery loves company, so here are a few of the many posting related to this error.

Continue reading →

Access – Lock File Issues

As of Patch Tuesday, Dec. 14th, 2021, there is a new Access file lock ‘bug’ as several threads have started popping up relating to error messages, such as:

This file is in use. Enter a new name or close the file that’s open in another program

Error 3050: Could not lock file.

in which longstanding databases no longer will open, can no longer be shared.

Here are a couple threads on the subject (there are many, many more, simple Google to find them):

Continue reading →

VBA’s FileLen Unreliable!

I’ve been working on a personal project in which I need to index files. As part of the indexing process I retrieve the file size.

The Problem With FileLen

For years, in various databases, I have always used VBA’s built-in FileLen Function to quickly and easily return the file size (in bytes) and never experienced any issue. Well, that was until today!

Sadly, I found out today that FileLen() is simply unreliable and that it returns negative values for certain files, thus crashing my application.

Continue reading →

Access – System Resource Exceeded

Today I thought I’d try and cover the subject of Access reporting back errors like:

System Resource Exceeded

There isn’t enough memory to perform this operation

What’s the Source of the Problem?

Many report these issues occurring on databases that were working fine for years and once they upgraded Access versions, the newer version would report such an error and then crash.

First, it is important to understand that Access does not access all of a computer’s RAM, so having 16, 32, 64 GB RAM changes nothing to the problem. Access has access only to a limited amount of RAM which depends on the bitness of your Access installation:

A 32-bit installation of Access has a hard limit of 2 GB of virtual memory (4GB total virtual memory => 2GB for Windows and 2GB of processing) regardless of what is physically available on the system itself
A 64-bit installation of Access has a hard limit of 8 TB of virtual memory (16TB total virtual memory => 8TB for Windows and 8TB of processing).

Note: The above information regarding the limitation of 32-bit and 64-bit installations comes from the youtube video on LAA given by Karl Donaubauer (Access MVP) for which a link is provided a little further in this post.

As such, a 64-bit version of Access can access orders of magnitude more RAM (if available) and it is thus highly unlikely to see such an error in an 64-bit installation.

Continue reading →