Access Broken today 10th May 2022

I have further information which may help to understand the problem.

My application has a client form and a bookings form. The client form has a subform with a list of that client's booking. The user can "drill down" from the client form to see the details of a booking on the booking form. When they do that, the application closes the client form and then opens the bookings form.

The following error message is displayed as soon as the bookings form is displayed:

The object doesn't contain the Automation object 'Blacklisted.'

The client form also has a function to create a new booking for the client. In this case, the application closes the client form and opens the booking form in data entry mode to create a new record.

When they do that, Access emits a beep (as if it is displaying an error message) but no message dialog is displayed. It then crashes.

Now what is of interest is that I have no objects/properties in the database called "Blacklisted". None. There are no fields, forms, controls or anything else called Blacklisted. However I do have a field on the client form called Blacklist and a client is considered to be "blacklisted" if that field is set.

So I used Brent Spaulding's excellent SearchForText utility ( https://www.utteraccess.com/topics/1992076 ) to search my database for "Blacklisted" and found a conditional format expression [Blacklisted] on the client name field of the client form. It is supposed to show blacklisted clients in red text.

NOTE: This is the form which is closing. The object name does not exist anywhere else in the database.

What this means is that once upon a time the Blacklist field was called Blacklisted and when it was renamed, the conditional format expression was not updated. As a result the conditional formatting is causing an error because it has a bad expression. However errors in conditional formatting expressions do not always surface, they just fail to cause the conditional formatting to be applied.

I removed the conditional formatting expression, and hence the source of the error.

Now when I drill down to the booking form, the following error is displayed:

No Current Record

(sound familiar?)

When I create a new booking record, the following error is displayed:

The Microsoft Access database engine does not recognize 'ContextListFill' as a valid field name or expression.

The system no longer crashes.

Now "ContextListFill" is a combo box filler function used as the ControlSource of a combo on both the closing client form and the opening booking form. Instead of crashing, Access appears to be displaying some other miscellaneous message about the closing form.

What is significant here is that this shows:

1. The error message is being displayed by Access as it closes a form. it is clearly trying to requery/refresh the dying form as it closes.
2. If Access cannot handle an error which occurs as the form closes, it crashes.

The crash appears to be Access's equivalent of us getting a Continue/Debug/End dialog in VBA if we don't handle a runtime error properly.

Although this is not a solution, it is a workaround which has allowed me to downgrade the severity of the error from a system crash to an irritating error message. I hope this information helps others to workaround the problem while Microsoft work on a fix.

Looks like a work around has been found, have a look here... https://www.access-programmers.co.uk/forums/threads/no-current-record-error-now-affecting-all-versions-of-my-database.323141/page-2#post-1825870

The workaround to use RecordsetClone instead of Recordset does not apply in my case. I have always used the RecordsetClone method.

Problem started today, version 2204. I can reproduce very easily:

• create a new database
• create a table
• create a form on the table
• add code to the form load event: Debug.Print Me.Recordset.Recordcount

Seems that any access to form's recordset in VBA causes problems.

PaulRoss_499 That's interesting.

I found that I had code in a forms open event that used

Me.Recordset.FindFirst "lngRecordID = " & lngRecordToJumpTo

I have replaced that with

  Dim recClone As Recordset 

  Set rst = Me.RecordsetClone 

  recClone.FindFirst "lngRecordID = " & lngRecordToJumpTo 

  Me.Bookmark = recClone.Bookmark 

  recClone.Close 

  Set recClone = Nothing

It now works without crashing as that form is closed, however, when I close the main form that closes the database I now get "No Current Record"