Object invalid or no longer exist

  • Thread starter Thread starter Iryna Roy
  • Start date Start date
I

Iryna Roy

Hello All,

I saw messages about this problem "Object invalid or no longer set" for A97,
2000 and now I see it in my application.
Actually not me, my customers.
I am using MS Access XP (Developer Edition) and Windows XP (with all updates
for Windows and Office installed) - everything is fine on my computer and
works properly. I don't have this error message.
However, when I distribute the database to customers, some of them have this
message and then #Name in all field and after first occurence this message
is appear everywhere, if you try to open any form. I noticed that on one
computer it starts to hapen after installing MS Office 2003 Beta.

Could you give me some advice, how to resolve the problem?

Best Regards,
Iryna Roy
 
I would suggest you to check to see if your customer's
access database is using the same library as you are.

Library can be found:
Go to VBE (Visual Basic Editor), under "Tools"
and "Preference".
 
JL said:
I would suggest you to check to see if your customer's
access database is using the same library as you are.

Library can be found:
Go to VBE (Visual Basic Editor), under "Tools"
and "Preference".

I believe that libraries are the same. I am distributing Runtime+MDE, they
are not able to check libraries ( I think so or is there any way to check it
in MDE?)
 
-----Original Message-----



I believe that libraries are the same. I am distributing Runtime+MDE, they
are not able to check libraries ( I think so or is there any way to check it
in MDE?)

You are right about checking library in MDE. I have try
it and the only way according to the help is to hit "F2"
and get a list of libraries. Maybe that will give you
some clue if you are missing any.
 
">
You are right about checking library in MDE. I have try
it and the only way according to the help is to hit "F2"
and get a list of libraries. Maybe that will give you
some clue if you are missing any.

Yes, you could hit it but just when you are in VBA Editor in MDB file.
"Unfortunatelly", everything is fine in my MDB. I have no errors. But in MDE
you could not hit anything, because there is no code there at all
 
I have opened my MDE file and hit Ctrl+G that will get me
to the VBA Editor. Then I hit "F2" that will give me
ojbect list, there is a "all library" which will list some
library in abbr.
Check to see if that is the same as your "MDB" file.

PS: I was just guessing that could be a library problem.
Because it has the same error message when the library is
not set correctly.
 
No luck, I checked all my workspace sessions, I am closing it by setting to
Nothing.
Any other idea, wha it could be? I am using ADO and DAO for different cases.
Could it be a problem? Do I need to use just ADO or just DAO?

Thank you for your help.
Best Regards,
Iryna Roy
 
:( Checked
I have this erorr in the form where I am using union queries. I have a main
form, than 4 subforms based on union queries. When I open the main form,
first time it works fine, when I update it first time it works, second
time - Object invalid or no longer set.

Doing the same steps on the other computers (not on one, I have around 20
working fine) and no probs. I have two computers working like this and one
computer which has #Name everywhere. In each form and in each field. Magic
#2. :(

HELP! I am dying

Thank you

Iryna Roy
 
How do you perform the update? The union query is read-only, so presumably
you run an UPDATE query or similar? Does it make any difference if you
requery after the update, i.e.:
Me.Requery

The fact that it works on some computers and not others suggests that this
may be related to the version/service pack differences. Look for
differences:

1. Help | About. What service pack?

2. Find msjet40.dll (typically in windows\system32). Right-click and check
the version number. Jet 4 SP7 will be 4.0.7328. Is this different on the
computer that has the problem than it is on the computer that does not have
the problem?

3. Find DAO360.dll (typically in \Program Files\Common Files\Microsoft
Shared\DAO). What version (e.g. 3.60.6508.2)? Any difference between the
machines that work and those that don't
 
Allen Browne said:
How do you perform the update? The union query is read-only, so presumably
you run an UPDATE query or similar? Does it make any difference if you
requery after the update, i.e.:
Me.Requery

The fact that it works on some computers and not others suggests that this
may be related to the version/service pack differences. Look for
differences:

1. Help | About. What service pack?

2. Find msjet40.dll (typically in windows\system32). Right-click and check
the version number. Jet 4 SP7 will be 4.0.7328. Is this different on the
computer that has the problem than it is on the computer that does not have
the problem?

3. Find DAO360.dll (typically in \Program Files\Common Files\Microsoft
Shared\DAO). What version (e.g. 3.60.6508.2)? Any difference between the
machines that work and those that don't


1. How could I find out about Service Pack, if I am installing run-time+mdb?

2. Here is the info from my comp:
MSACCESS.EXE - File Version: 10.0.4302.0



File Name: msjet40.dll - File Version: 4.0.7328.0



File name: dao360.dll - File Version: 3.60.6508.2


File name: msado25.tlb -File Version: 2.80.1022.0

This is info from another working computer:

MSACCESS.EXE 10.0.2627.1
Dao360.dll 03.60.6508.2
msjet40.dll 4.0.7328.0
msado25.tlb 2.71.9030.0

This is info from one problem computer:

MSACCESS.EXE 10.0.4302.0
Dao360.dll 03.60.6508.2
msjet40.dll 4.0.7328.0
msado25.tlb 2.80.1022.0

very funny :) Will re-do the updating part.
 
Back
Top