Refresh and Object errors in new installations

  • Thread starter Thread starter MK
  • Start date Start date
M

MK

Hi all,

I have an Access application (Access 2000), that is used by some 70
odd users. Lately (last month and a half), some users with new
installations (both, XP and W2K) experience different weird problems.

For example, I have a "continuous form", that when the user clicks a
button, there's a popup where they can edit that record. It works
perfectly on all computers, except in those new installations where
they have #ERROR in all number fields in the continuous form after
returning from the update form.

In another example, also a "continuous form" in the application, when
the user clicks on update, and closes the update form, they receive an
error "object invalid or no longer set". IE that the "continuous" form
has somehow closed.

Note: I tried installing all the windows and office service packs on
my computers, so that they mirror the users environements, but I can't
recreate it on my machines.

I took one computer, formatted it, installed W2K with service pack 3,
then updated to SP4, then installed office 2k SR1, and updated to
Office SP3, and lo and behold, the abovementioned problems where
there.

My question basically is, could there be anything in the
Windows-with-SP3 (Or WINXP-with SP2) installation, which could mess
around with subsequent office installations, or with the Jet engine?
Has anyone experienced or heard of something similar?


Thanks in advance for taking your time.

Mendel
 
MK said:
Hi all,

I have an Access application (Access 2000), that is used by some 70
odd users. Lately (last month and a half), some users with new
installations (both, XP and W2K) experience different weird problems.

For example, I have a "continuous form", that when the user clicks a
button, there's a popup where they can edit that record. It works
perfectly on all computers, except in those new installations where
they have #ERROR in all number fields in the continuous form after
returning from the update form.

In another example, also a "continuous form" in the application, when
the user clicks on update, and closes the update form, they receive an
error "object invalid or no longer set". IE that the "continuous" form
has somehow closed.

Note: I tried installing all the windows and office service packs on
my computers, so that they mirror the users environements, but I can't
recreate it on my machines.

I took one computer, formatted it, installed W2K with service pack 3,
then updated to SP4, then installed office 2k SR1, and updated to
Office SP3, and lo and behold, the abovementioned problems where
there.

My question basically is, could there be anything in the
Windows-with-SP3 (Or WINXP-with SP2) installation, which could mess
around with subsequent office installations, or with the Jet engine?
Has anyone experienced or heard of something similar?


Thanks in advance for taking your time.

Mendel
Click to expand...


On the machines that exhibit this error, one of the first things I
would check would be the Access References. With a code page open, go
to Tools > References and see if any are marked as Missing.

hth

Hugh
 
MK said:
Checked that already. All of the references are OK.

Any other suggestions?
Click to expand...


Well it was just a shot in the dark! I don't use Win2k or Access2k or
have that combination at any of my clients' sites, so I can only do
some guessing.

Number Fields may just give a clue. In later versions of Access, the
Table default value for numeric type Fields is zero. Previously it was
not. Just a Null. Does this info help at all?

Hugh
 
Back
Top