Access loses Relationships

Valerie

Registered User.
Local time
Today, 05:27
Joined
May 7, 2003
Messages
65
I have an Access 2000 database with upto 6 users. (split into Front end and Back end)

Whenever a user logs into the database he sees the message "You or another user may have unexpectedly quit MS Access while the MS Access database was open. Do you want access to attempt to repair."

The database has been compacted and repaired and also I have created two fresh database files and imported all of the objects.

Has anyone got any ideas what the problem might be?

Thanks in advance

Valerie
 
do you mean ldb files which don't belong to the currently opened database?
 
If you have a db "myDataBase.mdb" IN USE an associated file "myDataBase.ldb" will be open as well. When you close the DB (myDataBase.mdb) the associated LDB file (myDataBase.ldb) is erased. However if you have a power cut or some lazy "B" who don't shut the PC off correctly, then the LDB file remains and can cause you problems....
 
Networking collisions can also cause this problem. Or if someone has some networking hardware that occaisionally sends bad packets, the db can get corrupted. It's a known issue with access and jet, according to microsoft

According to the KB article,
There are three main reasons why an .mdb file may become corrupted, as follows:

* Interrupted Write Operation
* Faulty Networking Hardware
* Opening and Saving the .mdb File in Another Program

ed
 
Thanks for the reference to the MS Article - although it refers to Access 2002 and I am using Access 2000.

The article implies that the data should be moved to SQL Server for database being constantly used, which this one is.

Do you know how to check about network collisions?

Do you know if there would be any benefit in putting a copy of the Front End on each of the users PC rather than them all working with the same FE from the network?

Valerie
 
You should have a copy of the front end on each users PC, Thats the point of front end backend DB's
 
The only way I know of to test for faulty networking hardware is to use each network box exclusively for a period of time to see if you can recreate the corruption with that machine. Then you will know it is bad. As for packet collisions, I'm not too sure how to detect these.
 
To determine packet collisions, see your network manager, who probably has a statistics gatherer running on some computer.
 

Users who are viewing this thread

Back
Top Bottom