Access2000 Migration in a multi-user environment

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The situation appears to be this

We have got a small NT 4 network (30 users, with windows 95,98, me and 2000) all with MS Access 2000 SR-3, Jet4 installed.

We migrated from Access 97 to Access 2000 a month ago.
As we first installed it (SR-1), Access 2000 was completely unusable (crashing absolutely all the time). We then installed the database Jet engine 4 and the Service Release patch 3 for Access 2000.
Following the installation of these extra pieces of software, the situation has improved but is barely acceptable: we still keep crashing two or three times a day, we keep losing random primary keys and relationships between tables for no apparent reason, linked table keep losing the link.
Has anyone ever reported the same problem?

The situation is now so bad that we are even thinking of upgrading to a higher version of Access - or if the problem can’t be solved just use another database system.

Any help is appreciated
Thank you in advance

Benoit
 
While I did have significant stability problems with Access 2000 *during
development* we have not had any serious problems with it in production use.
I just talked to one of my colleagues, who looks after our largest Access
2000 customer. He tells me they haven't experienced any serious problems for
quite some time now. He had to install the service releases for Access 2000
and for JET 4, and we had to deal with the 'oplocks' issue. There's a KB
article that describes the 'oplocks' issue, and other information that you
may find helpful, at the following URL:
http://support.microsoft.com/default.aspx?scid=kb;en-us;303528

After we installed the service releases and dealt with the 'oplocks' issue,
both stability and performance have been satisfactory. One notable
difference between their environment and the one that you describe, however,
is that they are running Windows 2000 Server and, with the exception of a
small number of old Windows 9.x PCs, Windows 2000 Pro on most of the client
PCs.

Access 2002 requires Windows 98 or later, and Access 2003 requires Windows
2000 or later, so if you decide to upgrade to a later version of Access,
you'll have to upgrade the OS on some of those PCs, too.
--
Brendan Reynolds (MVP)
(e-mail address removed)

Benoit said:
The situation appears to be this:

We have got a small NT 4 network (30 users, with windows 95,98, me and
2000) all with MS Access 2000 SR-3, Jet4 installed.
We migrated from Access 97 to Access 2000 a month ago.
As we first installed it (SR-1), Access 2000 was completely unusable
(crashing absolutely all the time). We then installed the database Jet
engine 4 and the Service Release patch 3 for Access 2000.
Following the installation of these extra pieces of software, the
situation has improved but is barely acceptable: we still keep crashing two
or three times a day, we keep losing random primary keys and relationships
between tables for no apparent reason, linked table keep losing the link.
Has anyone ever reported the same problem?

The situation is now so bad that we are even thinking of upgrading to a
higher version of Access - or if the problem can't be solved just use
another database system.
 
Thank you for your quick answer.
We have installed the Service Releases for Access 2000 and Jet4. We haven't yet delt with the 'oplocks' issue. I suppose we should try that.
Shame a company like Microsoft puts on the markets products that don't seem to be yet fully tested.

Anyway, many thanks for your help. I'll let you know if this resolve the problem.

Benoit
 
Problem solved!

Changing the oplock setting in the server registry sorted all that mess out.

BIG thank you for your help.
 
Back
Top