Data Corruption Issue

[Cathy]

I'm maintaining a database that was created by someone else. Ever since it
was created it has had an issue with occasional record corruption. The data
is being added to header and detail type tables via a form and subform. The
header table is the table that gets the corrupted record. This table is
quite wide and has several data types... autonum, text, dates, memos, yes/no
checkboxes...

This database was created as a front end/back end design. It was roled out
to the user community before it was fully developed, so the decision was made
to create three front ends and put them into three different folders. The
users pick one of the three front ends for input. Data is input monthly
within a matter of hours by a minimum of 50 users. So the database is used
periodically, hard and fast. The corruption happens during these peaks.
Recently we found it is happening when two users are accessing the same
record at the same time. They are not using the same form at the same time.

What can be done to trouble shoot this problem further? What could be done
to allow record sharing more effectively? What can I check and add to this
e-mail to resolve this issue?

Thank you for your assistance in advance.

 

[Linq Adams via AccessMonster.com]

If you're saying that you have multiple users who are sharing one of three
front ends, i.e. say 20 users are using one copy in a shared folder, I
suspect that's the source of your corruption; shared front ends is a
recognized cause of repeat corruption You need to place a copy of the front
end (or even all three front ends) on each user's machine

 

[banem2]

I'm maintaining a database that was created by someone else.  Ever sinceit
was created it has had an issue with occasional record corruption.  The data
is being added to header and detail type tables via a form and subform.  The
header table is the table that gets the corrupted record.  This table is
quite wide and has several data types... autonum, text, dates, memos, yes/no
checkboxes...

This database was created as a front end/back end design.  It was roled out
to the user community before it was fully developed, so the decision was made
to create three front ends and put them into three different folders.  The
users pick one of the three front ends for input.  Data is input monthly
within a matter of hours by a minimum of 50 users.  So the database is used
periodically, hard and fast.  The corruption happens during these peaks. 
Recently we found it is happening when two users are accessing the same
record at the same time.  They are not using the same form at the same time.

What can be done to trouble shoot this problem further?  What could be done
to allow record sharing more effectively?  What can I check and add to this
e-mail to resolve this issue?

Thank you for your assistance in advance.

First advice is - repack both FE and BE into new, empty databases.
Once when you see any corruption of data, you could not be sure that
the database is 100% error free.

Then follow advice you got from Linq, each user needs to have its own
FE, while all of them share only one BE.

Regards,
Branislav Mihaljev, Microsoft Access MVP

 

[Cathy]

What is the best way to distribute the FE? We are still developing the FE,
so there will be regular changes....

Thank you,
Cathy

 

[banem2]

What is the best way to distribute the FE?  We are still developing the FE,
so there will be regular changes....

Thank you,
Cathy

Each user needs to have its own copy of FE. Assuming that the BE is on
this path \\SERVER\BE.MDB and when you have updated FE, re-link tables
using above UNC path and copy FE to each workstation. You won't need
to relink table on each workstation in this case.

Regards,
Branislav Mihaljev, Microsoft Access MVP

 

[Cathy]

Thank you!

Each user needs to have its own copy of FE. Assuming that the BE is on
this path \\SERVER\BE.MDB and when you have updated FE, re-link tables
using above UNC path and copy FE to each workstation. You won't need
to relink table on each workstation in this case.

Regards,
Branislav Mihaljev, Microsoft Access MVP