error message after changing the name of query.

[jalewis999]

I changed the name of a query because I found it useful in other procedures. I changed TestGifterLast to GifterLast. I then changed all references to it. I Mean All. I checked over and over, there is no mention of the original name anywhere. This query is used inside a busy loop. The only way out is to keep pressing ok. I did the same to TestGiftFirst with no problems.
I've tried deleting references to the query, saving and adding them back. No Luck. I've exited and reloaded. No luck. I took a copy of the query and pasted it as the old name. It stopped the message. But I don't like this kind of answer. Please can anyone help.
Win 10 newest Access.

[JoeM]

Make sure that you have also looked in places like:
- VBA code
- Calculated fields within a query
- Sorting fields

And make sure that you haven't misspelled it anywhere.

If it is used in many places, I would try to track it down to the lowest level (at the "base" level of any nesting), and see if you can find where it starts to be a problem, and focus your attention there.

[Micron]

I checked over and over, there is no mention of the original name anywhere.

I would bet money against you on that and I agree with the advice given. The problem reference could also be in a query stack (nested query). A forensic type of investigation might be required. You could also make use of the Database Documenter but you have to select the best options otherwise the document is usually too large to deal with.

[orange]

In other posts where this syndrome has prevailed, the suggestion was to try the free V-Tools utility to find source of the "ghost object".

[jalewis999]

You would win. Thanks

[jalewis999]

Yes you are all correct. I checked the code, but didn't remember I put it in a query when the DLast I was using proved to be unreliable. Thankyou all.

[Micron]

Ahh, the infamous DLast (or DFirst) function. I imagine you were using it on an unordered query or recordset, or worse, just a table?

[JoeM]

Yes you are all correct. I checked the code, but didn't remember I put it in a query when the DLast I was using proved to be unreliable. Thankyou all.

You are welcome.
Glad we were able to help!