All,
Have run out of ideas on a problem we have been having for a couple of weeks. We run w2k network with users using access2000 on a database with FE and BE components. The BE is resident on one of our servers with the FE on each local machine that needs it. The system has been running quite happily for a couple of years until.....
A couple of weeks ago users reported that they couldn't get into the BE database because of an error message saying 'invalid database...not recognised' etc etc. The only way round this was to access the BE database and repair it. This would fix it for a while until the same thing happened again a few hours later. Some users also reported the error 'object invalid or nolonger set'. Once this was seen then the system crashed again. However, if users were already in the system, they could continue working as if nothing had happened, until they came out and tried to get back in.
Steps I have taken so far are:
Checked system for viruses
Repaired the BE database
Decompiled and recomplied the FE and BE
Repaired and compressed the FE and BE
Re-linked the FE to the BE
Created a new blank BE and imported the data into it
Checked out the refs - all appear to be the same except some machines use MS access calendar control 7 instead of 9.
Moved the BE to another server altogether
Have now run out of ideas. No one user seems to be causing the system to fall over. Several user have reported they can't get into the system with the same result that the BE database becomes corrupt and invalid. Something is happening which is causing it to trip-out.
Any ideas are most welcome...
Yours in desparation....Andy.
Have run out of ideas on a problem we have been having for a couple of weeks. We run w2k network with users using access2000 on a database with FE and BE components. The BE is resident on one of our servers with the FE on each local machine that needs it. The system has been running quite happily for a couple of years until.....
A couple of weeks ago users reported that they couldn't get into the BE database because of an error message saying 'invalid database...not recognised' etc etc. The only way round this was to access the BE database and repair it. This would fix it for a while until the same thing happened again a few hours later. Some users also reported the error 'object invalid or nolonger set'. Once this was seen then the system crashed again. However, if users were already in the system, they could continue working as if nothing had happened, until they came out and tried to get back in.
Steps I have taken so far are:
Checked system for viruses
Repaired the BE database
Decompiled and recomplied the FE and BE
Repaired and compressed the FE and BE
Re-linked the FE to the BE
Created a new blank BE and imported the data into it
Checked out the refs - all appear to be the same except some machines use MS access calendar control 7 instead of 9.
Moved the BE to another server altogether
Have now run out of ideas. No one user seems to be causing the system to fall over. Several user have reported they can't get into the system with the same result that the BE database becomes corrupt and invalid. Something is happening which is causing it to trip-out.
Any ideas are most welcome...
Yours in desparation....Andy.