Solved Nz has started throwing up an error message

[sonic8]

You might get that sort of error if you have no records

^This!
I don't think NZ is to blame here. IMO, the situation that triggers the error is something outside the scope of NZ. The most likely cause is that you are trying to read data from a record when there currently is no record, as @gemma-the-husky already stated.

 

[Alc]

Firstly, thanks for all of those who suggested various causes and fixes.

The issue was finally resolved and it was one of those very annoying ones where the only symptom I was seeing that Nz stopped working but the cause was larger.

It seems that something happened during the latest software upgrade that screwed up Access itself. I removed it from the PC completely, rebooted, then reinstalled it. The problem is now gone.

I apologize if anyone spent too long trying to puzzle this out. Since the rest of the features seemed to be trouble-free, it never occurred to me that Access itself needed reinstaling.

 

[Gasman]

I would always try a repair first, but glad you got it all working again.

 

[The_Doc_Man]

It seems that something happened during the latest software upgrade that screwed up Access itself.

Oh, if only a couple of people ever saw this... but no, Microsoft, in their INFINITE wisdumb, does this now and then, affecting... well, potentially almost every country on Earth.

When I was with the Navy Enterprise Data Center, I ran some "tracking software" for cases where people reported issues like this, because we had to track EVERYTHING we did to change software configuration. I can't BEGIN to tell you how often we had a bad patch and everyone had to have a "push" of an update to fix the update. Let's just say it was not an uncommon occurrence.

Glad you traced it down to that, and PLEASE don't think you need to apologize for a Microsnort screw-up.