Repeat Access2000 Crash

  • Thread starter Thread starter buddy
  • Start date Start date
B

buddy

We are now using Access 2000 database on network with
about 10 cocurrent users. We don't have problem before,but
recently, it crashes very often. Everytime we repaire and
compact it, it can last very short time and then crash
again. Sometime we need to repaire database 7,8 times a
day. Also,It seems we can't compact database, everytime we
compact it, it'll have repeat crash followed.

Anyone can help?
 
Sounds like it might be time to go to SQL Server
or to a Microsoft Data Engine

I am taking the assumption that the DB is over 500 Mb
in size.

Thor
 
buddy said:
We are now using Access 2000 database on network with
about 10 cocurrent users. We don't have problem before,but
recently, it crashes very often. Everytime we repaire and
compact it, it can last very short time and then crash
again. Sometime we need to repaire database 7,8 times a
day. Also,It seems we can't compact database, everytime we
compact it, it'll have repeat crash followed.

Sounds like the OpLocks problem.

Access 2000 and newer has some problems with Win NT 4 and Windows 2000
servers commonly known as the oplocks fix. The most common problem
besides the opslock problem is intermittently flaky hardware.

Another common problem is sharing the MDB containing the queries,
forms, reports, macros and modules on a server. You really want to
split the MDB. See the "Splitting your app into a front end and back
end Tips" page at my website for more info. See the "Auto FE Updater
downloads" page at my website to make this relatively painless..

Users must not use abruptly terminate Access such as by cancelling the
job using Task Manager or by powering off their system without doing a
shutdown first. IPX has also been a problem.

Ensure that all users are at the same Access SR level and Jet SP.
Preferably the latest one. (I use the various API calls available
and am checking the version number, size and date/time of a crucial
dll, MSJET35/40.DLL, to ensure it matches what I have on my system.)
See the "Verify Appropriate Jet Service Pack is installed" page at my
website.

There are other causes of corruption mentioned on my website.

Peter Miller has stated that you should always import all objects in a
repaired MDB into a new MDB as there may be minor corruption still
left which can get worse over time.

For more information on corruption including a more links, official MS
KB articles and a list of vendors who state they can fix corruption
see http://www.granite.ab.ca/access/corruptmdbs.htm

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
 
Thor said:
Sounds like it might be time to go to SQL Server
or to a Microsoft Data Engine

Rubbish. There are valid reasons for going to SQL Server but
frequent corruptions aren't a good ones.
I am taking the assumption that the DB is over 500 Mb
in size.

Any particular reason why you think 500 Mb is a problem?

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
 
Back
Top