Avoid File Corruptions

[Samuel]

I split the Access file to data and front end to avoid further file
corruption.

Since the boss got very concerned from possible future file corruptions I
would like to do the best to avoid it

Will it be beneficial to start using SQL server instead to avoid any loss of
data?

Thank you,
Samuel

 

[Tony Toews [MVP]]

I split the Access file to data and front end to avoid further file
corruption.

That is indeed one of the biggest causes of corruption in A2000 and
newer.

Each user is getting thier own copy of the FE too, right?

Since the boss got very concerned from possible future file corruptions I
would like to do the best to avoid it

Go through the long list at Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm
Start at the top and work your way down.

The above said did you lose any data in your corruptions? If not I
would suspect it was the combined

Will it be beneficial to start using SQL server instead to avoid any loss of
data?

That would greatly reduce the possibility of MDB corruption.

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/

 

[John W. Vinson]

Since the boss got very concerned from possible future file corruptions I
would like to do the best to avoid it

Will it be beneficial to start using SQL server instead to avoid any loss of
data?

If you are willing to put in the extra work (not only of setting up the
database but doing the database administration which SQL/Server requires, such
as maintining backup policies, user permissions, etc.), sure. SQL data can get
corrupted too, however, it's not a cure-all.

See http://www.granite.ab.ca/access/corruptmdbs.htm for information on
preventing corruption; Tony also has some thoughts on SQL conversion on his
page.

John W. Vinson [MVP]

 

[Arvin Meyer [MVP]]

I split the Access file to data and front end to avoid further file
corruption.

Excellent. Now make sure that each user has a copy of the front-end on their
workstation.

Will it be beneficial to start using SQL server instead to avoid any loss
of data?

SQL-Server can corrupt too. Actually the worst 2 data corruptions I've ever
seen were on SQL-Server. Any file can corrupt. However, if properly
designed, backed-up and maintained, SQL-Server is capable of recovering all
the data. Of the 2 that were corrupt that I have worked on. One wasn't
properly backed up but I was able to recover all the data using Access to
connect to the database. The other wasn't properly maintained and the logs
were too large to dump because of disk space. All the data on that one was
lost.

I have had very few problems with Access corruption. In almost 15 years,
I've only lost about 20 records. Most Access corruption is recoverable, but
not all, so it's important to backup regularly. The last corruption of an
Access database that I had to deal with was in April of 2003 when a bad WiFi
card kept dropping connections. No records were lost.