Prevent Database Crash

  • Thread starter Thread starter paul
  • Start date Start date
P

paul

Hi,
I have an Access 2000 application, with Front & Back end
both stored in the file server. The system has about a
dozen of users. It's crash this Morning, with error
message "You or another user may have unexpectedly quit
Microsoft Access while a database was open". I was abled
to fix that, but how can I prevent it strike again? Any
direction I can follow? What area I need to improve?
Thanks a lot.
 
Hi,
I have an Access 2000 application, with Front & Back end
both stored in the file server. The system has about a
dozen of users. It's crash this Morning, with error
message "You or another user may have unexpectedly quit
Microsoft Access while a database was open". I was abled
to fix that, but how can I prevent it strike again? Any
direction I can follow? What area I need to improve?
Thanks a lot.
Click to expand...

User training, for one. Some users get impatient and ctrl-alt-del and
stop Access (or even power down their PC) when a query runs too long.
Explain gently that this is very like turning off the ignition at
65mph on <local crowded highway of your choice> and is grounds for
disciplinary action.

And KEEP DAILY - at least - backups, of course.

See http://www.granite.ab.ca/access/corruptmdbs.htm for a lot of very
good tips on prevention and cure of database corruption.
 
paul said:
Hi,
I have an Access 2000 application, with Front & Back end
both stored in the file server.
Click to expand...

You put the front ends on the user's machines!
 
Hi,
I have an Access 2000 application, with Front & Back end
both stored in the file server. The system has about a
dozen of users. It's crash this Morning, with error
message "You or another user may have unexpectedly quit
Microsoft Access while a database was open". I was abled
to fix that, but how can I prevent it strike again? Any
direction I can follow? What area I need to improve?
Thanks a lot.
Click to expand...


Hmm_ Seems like a poor environment for a desktop database program. Once the
'user' pool exceeds 1_ I normally consider moving the data storage to sql or
whatever and using access only as the front end component.
 
Hmm_ Seems like a poor environment for a desktop database program. Once the
'user' pool exceeds 1_ I normally consider moving the data storage to sql or
whatever and using access only as the front end component.
Click to expand...

And yet I have clients with 25 users in with very few problems.

Tony
 
Back
Top