Database Repair Help

[Johnson]

I created an Access database in Access 2000 and share it on a WNT4.0 server.
Several intermittent times a day the database requires rebuilding when you
attempt to open it on one of several workstations. Some of the workstations
have Access 2000 and some have Access 2003. No more than 7 users are on the
database simultaneously and usually lesss than 4. If you have the file open
on your computer prior to the need repair dialog box popping up on one of
the other workstations you can still use the database and your data will be
saved but no new users can open the file until it is closed on each
workstation and repaired. Any ideas on how to permanently repair the
database would be greatly appreciated. Thanks in advance.

 

[Tony Toews [MVP]]

I created an Access database in Access 2000 and share it on a WNT4.0 server.
Several intermittent times a day the database requires rebuilding when you
attempt to open it on one of several workstations.

Unfortunately there could be a large number of causes. Are any users
getting a "Disk or Network Error"? Are there any wireless networks in
use?

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

If you have the file open
on your computer prior to the need repair dialog box popping up on one of
the other workstations you can still use the database and your data will be
saved but no new users can open the file until it is closed on each
workstation and repaired.

This is standard behavior. Access only checks to see if the MDB is
possibly corrupted when it opens the MDB the first time. Once the
user is in the MDB it doesn't bother checking any more.

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

 

[George Nicholson]

Tony:
I don't see anything in the OP's post to indicate that they're working
with a split database.

I also don't see anything on your (excellent!) site under "Corruption
Causes" that, ahem, cautions?, against multiple users sharing the same FE
simultaneously (whether split or not). That could potentially cause constant
corruption like the OP is experiencing, would it not?

George

 

[Tony Toews [MVP]]

I don't see anything in the OP's post to indicate that they're working
with a split database.

Good point. I should've picked up on that.

I also don't see anything on your (excellent!) site under "Corruption
Causes" that, ahem, cautions?, against multiple users sharing the same FE
simultaneously (whether split or not). That could potentially cause constant
corruption like the OP is experiencing, would it not?

I'm sure there is something there... <smile> Sure, third paragraph
at http://www.granite.ab.ca/access/corruption/causessoftware.htm

If not already done split the MDB into a front end and back end and
ensure your users are using their own copy of the front end. See the
free Auto FE Updater for assistance in this latter task. This is
particularly troublesome in Access 2000 and very noticeable after just
converting from Access 97.

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

 

[George Nicholson]

My bad. I didn't look carefully enough. Should have known better

 

[Tony Toews [MVP]]

My bad. I didn't look carefully enough. Should have known better

It's a long, long page.

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