Write conflict errors and how to manage

[Ruegen]

Occasionally the users in our database will try to open and edit the same record (admin might be editing the record, ask the user to open their record and then the problem occors)



I get ########### errors on some fields, it locks everybody out, I have to do a compact and repair.

I get the message first like in the link

http://support.microsoft.com/kb/304181

I'd like to know how to avoid this, how to handle this, how to get away from database corruption etc.

advice?

[June7]

Don't let both edit the same record. One can edit and the other can view at same time.

Is this a split db?

I've never had lockout with split db.

[Ruegen]

Don't let both edit the same record. One can edit and the other can view at same time.

Is this a split db?

I've never had lockout with split db.

Yes, assuming you mean split db means more than one user uses the database?

[June7]

Split means two files - frontend and backend.

Backend has data tables and sits on a common file server.

Frontend is user interface to data - has queries, forms, reports, code, and links to backend tables.

Each user has a copy of the Frontend on their workstation.

[Ruegen]

Split means two files - frontend and backend.

Backend has data tables and sits on a common file server.

Frontend is user interface to data - has queries, forms, reports, code, and links to backend tables.

Each user has a copy of the Frontend on their workstation.

Yup. That's our setup.

Each user has a 14MB front end and the backend is 150 odd mb

[June7]

Has been a couple times two users tried to edit same record and generated an error but no lockout, just didn't save edits and one user had to redo theirs. Our work flow makes this very difficult to occur.

There really should not be any issue with a second user just viewing the record. If there is some code that is trying to edit the record, that will produce same impact as a user manually editing.

[Ruegen]

Has been a couple times two users tried to edit same record and generated an error but no lockout, just didn't save edits and one user had to redo theirs. Our work flow makes this very difficult to occur.

There really should not be any issue with a second user just viewing the record. If there is some code that is trying to edit the record, that will produce same impact as a user manually editing.

I thought it might be something like that. Generally every staff member has their own area of records, they can view other schools when searching (in case they receive a random call) but generally are restricted to their own areas to call.

Admin from time to time will go in and edit. It may be that there is some autocode when the record is opened and then when admin asks staff to open the same record that is when the conflict occurs.....?

[June7]

Yes, but it is the ######### and lockout I find odd. That has never happened to us.

[Ruegen]

Yes, but it is the ######### and lockout I find odd. That has never happened to us.

one of the users opened a record, err in memo field of the form then when I edited the record the field had wiped the data in the field and replaced it with ##########

I cleared it and pasted data from a backup.

I was told this used to happen to the old database from time to time from which most of the data has come from...

[June7]

What was 'old database'? Earlier Access version?

This is mysterious.

[Ruegen]

What was 'old database'? Earlier Access version?

This is mysterious.

Yes old 2000. Most of the data is imported using append though so they should be new tables...