Object invalid or no longer set

[4bex]

Hello there,
I am trying to get to the bottom of an 'Object invalid or no longer set' issue, but I am not a database programmer.

We have approx 20 users on MS Access 2002 front ends on 2 sites connected by WAN using a SQL 2000 SP4 database backend.

1 site is 24 hours, the other is 9 - 5 operation.

We have a SQL database at both sites using replication. Every 10 minutes the data entered at 24hr site is uploaded to 9-5 site and then merged.

We get intermittent 'Object invalid or no longer set' message pop up on the 24hr site. However having closely monitored the activity it only occurs when there are users usiong the database on the 9-5 site. After a merge has taken place the 'object invalid' message can pop up on 1 workstation at the 24 hour site.

Both sites are running Windows XP SP2 and MS Office XP Pro SP3 (so MS Access 2002 with SP3)

I have checked that all machines are running the correct version of MSJET40.DLL and they all have the correct version 4.0.8618.0

There are no run-time error numbers or any events in Event viewer on the workstations. There are no network connectivity problems (continuous pings from suspect workstation to db server and back again show no loss at all)

Curiously once the 9-5 site have gone home the error never occurs at he 24hr site.

Also the users that experience this don't actually have to be active in the Access front-end.

My first question is, Would this be an Access or SQL issue?

Any pointers woudl be very helpful.

[zzqxxq]

Here is what Microsoft says about the error:

SYMPTOMS
When opening and closing connections or recordsets using the Microsoft ODBC Driver for Access or the Microsoft OLE DB Provider for Jet, the following error may be reported:
Object invalid or no longer set.
After this error is reported, no more recordsets or connections can be opened from the same process.

Other possible error messages reported to the client application include:
Too many tables open.
Cannot open any more tables.

RESOLUTION
To resolve this problem, install the latest Microsoft Jet 4.0 service pack 6. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. (I put them below) This problem was fixed in Jet 4.0 Service Pack 6 (SP6).

Here is the link to the article on the MS Website:
http://support.microsoft.com/default...;en-us;Q304536

• Microsoft Open Database Connectivity Driver for Access 4.0
• Microsoft OLE DB Provider for Jet 4.0

Hope that helps

[4bex]

Thanks for that, but have already been down this road.
All machines are XP SP2 so have correct version of MSJET40.dll as stated in my original message and according to the microsoft article.

If it is a jet problem - why does it not happen to the machines at the 9-5 site and why does it not happen when the 9-5 site has gone home?

The behaviour is not the same as described in Microsoft article as all the user has to do is o.k. the error message and they can continue working.

We can also have data updates all day from both sites and not have a single object invalid then sometimes there will be 1 a day on different machines and different users.

Thanks for pointer anyway, but it is not a jet issue.