Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Object Invalid Or No Longer Set" Error Message

Status
Not open for further replies.

jaaret

Instructor
Jun 19, 2002
171
I have a form in Access XP that works on my home laptop but often comes up with the dreaded "Objectd invalid or no longer set" at work (also on Access XP).

Here are the symptoms: the main form pulls a TransID (Transaction ID) on a Transactions subform. The TransID drives all the other subforms on the main form. When this error occurs the Date and Time fields on the Transactions subform suddenly display: "#Name?", the other subforms go blank, and the "Object invalid or no longer set" error comes up. If I close and reopen the main form it will work fine - for a while.

Since this error never occurs on my home laptop I think it may have to do with a particular object library not being registered on my work computer (this is one of Help's suggestions on the error message).

Any insights or ideas?

Thanks,
Jaaret
 
Can you post the code that is causing the error?

Ken S.
 
Thanks, Eupher. Based on your response I started removing code. Removing all instances of .requery cured the problem (i.e. Forms!frmTransactions!sfrmTransactions.requery). Now the form doesn't error out but it doesn't autmatically update, either. I'll search for threads addressing updating forms and subforms...

Jaaret
 
Hi Jaaret,

I'm having the exact same problem. If I remove the .requery the error goes away but I don't get the desired affect. The thing that's getting me is that my front end is installed on about 50 different computers. None of them have this symptom. I would be interested if you find an answer.
Thanks,
Eightball
 
I don't know if this is the cause in your case, but I also have an access front end installed on about 20 machines and had started noticing a few of them giving me that error. I have found that I only get the error on machines running Windows 2000 SP4. All my SP3 machines work great. Also, the scary part is that I use SP4 on my development machine, but I don't get the error. I'm using Access 2000 by the way.

The only workaround I have found is to not install SP4. Any help on this would be great because I believe in keeping updated with service packs.
 
I checked, and yes, I'm running Win 200 SP4. This explains why my forms work just fine on my Win XP machine at home!

I'm going to have them roll me back to SP3 unless someone has a better suggestion.

Thanks for the information!
Jaaret
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top