I have run into a problem with vba code sometimes not working.
I had a perfectly good Access Database (or so it seemed to me) until one day the vba code on the double click event to open a form to edit details in another form, stopped working.
I could not resolve the problem, until I remembered the last change I had made to the form.  I opened it with the RecordSource as AccountQ (which was ordered in a descending order) instead of AccountT (upon which Account Q was based).
I changed it back to AccountT and everything worked again.
I later, (after having closed and reopened the database, but without having turned my computer off), changed it back to AccountQ and again everything worked!!!
I can only assume therefore that somehow or other the vba code was remembered during the period the database was shut.
Would I be right?
David

---

Reply from Richard Rost:

I've never experienced this before, but I have had weird problems that you futz with for hours and then all of the sudden just inexplicably fix themselves. I don't know of any latency problem as you suggest, but I do know that Gremlins are real, and they sometimes live inside your database.