Database Conflicts and Repairs

  • Thread starter Thread starter Stan
  • Start date Start date
S

Stan

I have a multiuser DB store on a network drive. When the
DB opens in opens to a Multitab form. The form is a read
only form. User select from the form a project and can
view different info for the project on each tab.

I have the Option Advance set to the defaults. I keeping
getting that the DB needs to be rebuilt message on a
somewhat regular basis. Once I get all of the users off
the DB it maybe takes 10 seconds for the rebuild.

How can I avoid having this problem of DB corruption?
 
Just to get the ball rolling for you, the most common
solutions my group has for this is to archive any table
data possible to a backup database to reduce the db size
and compact the database from the tools->database utilities
menu. The compact creates a new db that you can then
rename and make it "live". Our multi-user db's tend to
lose stability as the size approaches 10 Megs - access just
isn't all that great at handling multi-users.

Also consider that people who don't properly close the
access application while working in tables - eg. forcing a
close of the app. or rebooting their computer while a
procedure is running, might be causing the need for repair.
If any specific report or form is causing the problem, you
might want to recreate it (last resort). My last tip is
starting a new database and importing the tables, queries,
etc. If it doesn't import forms and reports, copy and
paste them in.

good luck
rob
 
-----Original Message-----
I have a multiuser DB store on a network drive. When the
DB opens in opens to a Multitab form. The form is a read
only form. User select from the form a project and can
view different info for the project on each tab.

I have the Option Advance set to the defaults. I keeping
getting that the DB needs to be rebuilt message on a
somewhat regular basis. Once I get all of the users off
the DB it maybe takes 10 seconds for the rebuild.

How can I avoid having this problem of DB corruption?
Click to expand...

first thing is to compact/repair *every night* after all
the users log off. Should be the last thing you do before
leaving each night. Remember to make a copy of the db
before you do the compact/repair, just in case.

Also, if you haven't done so already, split the database,
and make each user copy the front-end to their own machine.
 
Back
Top