Access 97 with 2000 and multiuser environ.

  • Thread starter Thread starter Tendi Henry
  • Start date Start date
T

Tendi Henry

Hello,

I have a multiuser db with 20,000 records that was
orginally in access 97. We upgraded 3 user to windows 2000
and thus have database file being accessed using access 97
and 2000.(we're converting totally to access 2000 soon)

The past couple of days we've been crashing and getting the
error msg "The microsoft jet database engine cannot opoen
the file (file name). It is already opened exclusively by
another user, or you need permission to view its data"
I've recently updated the jet database engine with the
patch msjet3.5sp3.

I have no clue...what could be wrong? please help.
 
Tendi Henry said:
I have a multiuser db with 20,000 records that was
orginally in access 97. We upgraded 3 user to windows 2000
and thus have database file being accessed using access 97
and 2000.(we're converting totally to access 2000 soon)

The past couple of days we've been crashing and getting the
error msg "The microsoft jet database engine cannot opoen
the file (file name). It is already opened exclusively by
another user, or you need permission to view its data"
I've recently updated the jet database engine with the
patch msjet3.5sp3.
Click to expand...

Access 2000 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.

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