In Access, FIND AND REPLACE "is null" doesn't work.

Anonymous
2020-08-27T16:57:49+00:00

Brand new install of Office 365 on brand new desktop.

In Access, FIND AND REPLACE "is null" doesn't work.   "Find next" button works, but then both "Replace" and "Replace All" buttons return "search item not found."  Screen shot shows a brand new test data base to show this.  FIND "is null" successfully moved to the next empty field.  Then clicking on "Replace" or "Replace All" returns "Not Found".    All this is a change from what worked in previous Access. 

I saw this problem on this forum from February 2020 but it remained unresolved.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} vote

10 answers

Sort by: Most helpful
  1. Tom van Stiphout 40,091 Reputation points MVP Volunteer Moderator
    2020-08-28T23:32:37+00:00

    What is the data type of the field in question?

    Short Text may be working differently than Long Text.

    0 comments No comments
  2. Anonymous
    2020-08-31T15:50:26+00:00

    Here's my Access for the test db that doesn't find "is null".  The field is SHORT TEXT.

    0 comments No comments
  3. Anonymous
    2020-08-31T15:53:52+00:00

    Same error when fields are LONG TEXT.

    0 comments No comments
  4. Tom van Stiphout 40,091 Reputation points MVP Volunteer Moderator
    2020-08-31T23:52:34+00:00

    Thanks Mark. We have a reproducible scenario. It's now on the backlog.

    Thank you for reporting it!

    0 comments No comments
  5. Anonymous
    2020-09-02T03:31:38+00:00

    I checked previous versions, and although this came close to working properly in Access 2010, I would say it has never been without issue.

    For example, in 2010, doing a Replace All with 'is null' will replace both nulls, and zero-length strings, which is not correct behavior.

    Shane Groff

    Access Engineering

    0 comments No comments