Corrupted Records

[Francois]

I have a fairly large database (Access 2007) on a server and about 15 people
are working on it simultaneous. Every now and again in one of the primary
tables a corrupted record is generated with the following characters in the
cells of the fields: "äµä¥å‰„ä¹ï½„凾ã–ã„´". When this happens I loose the data of that
specific record.

What can be the cause of this and how can I prevent this from happening?

 

[Rick A.B.]

I have a fairly large database (Access 2007) on a server and about 15 people
are working on it simultaneous.   Every now and again in one of the primary
tables a corrupted record is generated with the following characters in the
cells of the fields:  "äµä¥å‰„ä¹ï½„凾ã–ã„´".  When this happens I loose the data of that
specific record.

What can be the cause of this and how can I prevent this from happening?

Francois,

Is your database split into front end on users computers and backend
on network server? If not that's more than likely the cause of your
problems.

Hope that helps.

Rick

 

[John W. Vinson]

I have a fairly large database (Access 2007) on a server and about 15 people
are working on it simultaneous. Every now and again in one of the primary
tables a corrupted record is generated with the following characters in the
cells of the fields: "????????". When this happens I loose the data of that
specific record.

What can be the cause of this and how can I prevent this from happening?

As Rick says... *split your database*, as soon as possible. Sharing an unsplit
database among users on a network is simply not as reliable.

See:

http://www.granite.ab.ca/access/splitapp.htm
http://www.granite.ab.ca/access/corruptmdbs.htm

for more details.

 

[Tony Toews [MVP]]

Is your database split into front end on users computers and backend
on network server? If not that's more than likely the cause of your
problems.

Actually I rather doubt that splitting will help with corrupted
records. Splitting is a very good idea and helps with other
corruptions but not, in my opinion, with corrupted records.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Francois]

Hi Rick,

Thanks for your reply. Yes I have split the database into a backend on a
server and a frontend on each user's pc. So I guess it cannot be that?? The
database was originally done in Access 97 and I converted it to 2007. Do you
think that can be the problem?

Francois

 

[Rick A.B.]

Hi Rick,

Thanks for your reply.  Yes I have split the database into a backend on a
server and a frontend on each user's pc.  So I guess it cannot be that?? The
database was originally done in Access 97 and I converted it to 2007.  Do you
think that can be the problem?

Francois

Franciois,

One thing that comes to mind would be network problems on one of your
workstations, a bad NIC or connection dropping out. Do you use any
kind of Audit Trail to see who adds modifies or delete's records?
Something like that would at least give you a clue if it's a network
issue. I'm sure Tony or John or others will have some good
suggestions.

Hope that helps

Rick

 

[Tony Toews [MVP]]

I'm sure Tony or John or others will have some good
suggestions.

Everything I know about corruption is on my website. And I don't
have any specific suggestions for Francois's posting.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/