Hi there. I've written code to requery a listbox. No big deal right? (Listbox.requery). The listbox is not requerying though. Has anyone encountered this problem before?
I've been working on this DB for some time now and this is the first time I've come across this problem.
Thanks.

Where are you putting the code and in response to what?

A simplified explanation...The listbox shows the results of a table. The code is in response to clicking a button. The button adds a new record to that table. So after a new record is added, the code requeries the listbox to show the user that a new record has been added to the table.
I have used the requery method effectively several times in the past and consider myself rather proficient at (if nothing else) using this requery method. This, however, is something I have not seen and it just started to happen recently to a DB that I've been working with for some time now.
This is only one of a list of several "quirky" problems I've run into with Access recently. I may be mistaken, but I believe that this could be an issue with Access itself. Somehow I may have overwhelmed the DBMS. I've been told that Access is not the most robust DBMS available and this could be one of the reasons why.
In addition: I've run the utility that repairs the DB and also restarted the PC, but this hasn't helped either.

Yes access has some strange habits at times you could try importing everything into a new blank database, compile modules and then compact usually does the trick. I've never found the repair utility to useful for anything.
HTH

Rich,
Thanks for the tip. I'll definitely try your advice and get back. The increased occurrence of these weird "quirks" really threw me for one.
BTW:An earlier problem I had was that the DBMS couldn't recognize an open subform. I double-checked my spelling of the subform name, but I still couldn't understand why Access couldn't see it. Then I simply cut out and pasted the subform back to where it was in the first place. To my surprise, this fixed the problem.
Then after this requery problem happened, I had my suspicions of the entire DBMS.
The only conclusion I had was that with all the copying and pasting of controls I've been doing, I must have confused the thing somewhere along the way.
Thanks again.