Windows 2000 Server and Acess 2000 constant corruption

[Mark C.]

The company I work for has been running Access 2000 on a Windows NT
server with Opportunistic Locking turned off on the server without
issue for almost a year. We have just switched to a Windows 2000 file
server with service pack 3 installed and are now experiencing at least
2 corruptions a day. The registry setting for Opportunistic Locking
that was on the Windows NT server does not exist on the Windows 2000
server so we can not make the needed change to the new server. From
what I understand service pack 3 is supposed to take care of this
problem. Does anyone have any suggestions on how to procced? Any help
would be appreciated as this has caused a very unstable work
environment.
Regards,
Mark C.

[Tony Toews]

he******@yahoo.com (Mark C.) wrote:

The company I work for has been running Access 2000 on a Windows NT
server with Opportunistic Locking turned off on the server without
issue for almost a year. We have just switched to a Windows 2000 file
server with service pack 3 installed and are now experiencing at least
2 corruptions a day. The registry setting for Opportunistic Locking
that was on the Windows NT server does not exist on the Windows 2000
server so we can not make the needed change to the new server.
Add the registry setting as per the KB article Configuring Opportunistic Locking in
Windows http://support.microsoft.com/?kbid=296264 and reboot.
From
what I understand service pack 3 is supposed to take care of this
problem.

But Win 2000 SP3 must also be installed on all the client systems as well.

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

[Mark]

Tony,

Thanks for your help but the changes you mentioned did not help.

The registry setting was added on the server side and all the client
machines already have service pack 3. We had a total of 5 corruption's today
in 2 different databases.

We had a rep. from Microsoft on the phone today and he thinks that it is not
Ops Locks that is the problem. He told us that the MSJET DLL that we are
using is old but this is the same DLL we used in the Win NT server
environment with no corruption's. We made the change this evening with the
DLL and just have to pray that it works. Microsoft told us to try this
first and if it does not work to call them back. Do you think they know what
they are talking about? If anyone has any insight to this type of problem
please by all means help us out. I guess if all else fails we can go back to
the Win NT server were we had no corruption's but eventually we have to
upgrade.
Regards,
Mark
"Tony Toews" <tt****@telusplanet.net> wrote in message
news:44********************************@4ax.com...

he******@yahoo.com (Mark C.) wrote:

The company I work for has been running Access 2000 on a Windows NT
server with Opportunistic Locking turned off on the server without
issue for almost a year. We have just switched to a Windows 2000 file
server with service pack 3 installed and are now experiencing at least
2 corruptions a day. The registry setting for Opportunistic Locking
that was on the Windows NT server does not exist on the Windows 2000
server so we can not make the needed change to the new server.
Add the registry setting as per the KB article Configuring Opportunistic

Locking in Windows http://support.microsoft.com/?kbid=296264 and reboot.

From
what I understand service pack 3 is supposed to take care of this
problem.

But Win 2000 SP3 must also be installed on all the client systems as well.

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

[David W. Fenton]

he******@yahoo.com (Mark) wrote in
<ZO********************@comcast.com>:

The registry setting was added on the server side and all the
client machines already have service pack 3. We had a total of 5
corruption's today in 2 different databases.

We had a rep. from Microsoft on the phone today and he thinks that
it is not Ops Locks that is the problem. He told us that the MSJET
DLL that we are using is old but this is the same DLL we used in
the Win NT server environment with no corruption's. We made the
change this evening with the DLL and just have to pray that it
works. Microsoft told us to try this first and if it does not work
to call them back. Do you think they know what they are talking
about? If anyone has any insight to this type of problem please by
all means help us out. I guess if all else fails we can go back to
the Win NT server were we had no corruption's but eventually we
have to upgrade.

Are the Access installations at least SR1a+ and at least Jet
4 Service Pack 6? If not, you'll continue to experience corruption.
Once you have that in place in 100% of workstations (even one out
of 100 will cause corruption), the you can start looking at other
sources of problems.

I've been through this dozens of times -- SR1a or later plus Jet 4
SP6 is the minimum safe installation of Access 2000. Anything less
is going to cause corruption eventually.

And don't just guess -- check every single workstation. At my
largest installation (about 40 workstations) I put in code that
logs Access version and Jet version in a central table when the
users log in so I can always check who is running what version of
Access (and, yes, workstations revert when they are rebuilt by
techs who don't know what they need to do to fully re-install
Access).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Tom van Stiphout]

On Mon, 22 Dec 2003 21:40:48 -0800, "Mark" <he******@yahoo.com> wrote:

It's a very good idea to be current on Jet service packs. Jet4SP8 is
the latest version.

-Tom.

Tony,

Thanks for your help but the changes you mentioned did not help.

The registry setting was added on the server side and all the client
machines already have service pack 3. We had a total of 5 corruption's today
in 2 different databases.

We had a rep. from Microsoft on the phone today and he thinks that it is not
Ops Locks that is the problem. He told us that the MSJET DLL that we are
using is old but this is the same DLL we used in the Win NT server
environment with no corruption's. We made the change this evening with the
DLL and just have to pray that it works. Microsoft told us to try this
first and if it does not work to call them back. Do you think they know what
they are talking about? If anyone has any insight to this type of problem
please by all means help us out. I guess if all else fails we can go back to
the Win NT server were we had no corruption's but eventually we have to
upgrade.
Regards,
Mark
"Tony Toews" <tt****@telusplanet.net> wrote in message
news:44********************************@4ax.com.. .

he******@yahoo.com (Mark C.) wrote:

>The company I work for has been running Access 2000 on a Windows NT
>server with Opportunistic Locking turned off on the server without
>issue for almost a year. We have just switched to a Windows 2000 file
>server with service pack 3 installed and are now experiencing at least
>2 corruptions a day. The registry setting for Opportunistic Locking
>that was on the Windows NT server does not exist on the Windows 2000
>server so we can not make the needed change to the new server.

Add the registry setting as per the KB article Configuring Opportunistic

Locking in

Windows http://support.microsoft.com/?kbid=296264 and reboot.

>From
>what I understand service pack 3 is supposed to take care of this
>problem.

But Win 2000 SP3 must also be installed on all the client systems as well.

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

[Red]

"David W. Fenton"

And don't just guess -- check every single workstation. At my
largest installation (about 40 workstations)

40 workstations .... with linked tables to SQL Server?

Bye: Red

[David W. Fenton]

xx**@usa.net (Red) wrote in
<SI*********************@twister2.libero.it>:

"David W. Fenton"

And don't just guess -- check every single workstation. At my
largest installation (about 40 workstations)

40 workstations .... with linked tables to SQL Server?

No, to an MDB. 25 or so of the users are read-only. Of the
remainder, only 6 or so of them ever edit more than one table. Of
the remainder, the editing is very sporadic, mostly adding records,
not editing. The actual user load at any particular time is
substantially lower than the number of workstations would imply.

In any event, that app has version checking because it's just too
easy for the workstations to get rebuilt/replaced and no longer
have the proper version of Access/Jet.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

to*****@no.spam.cox.net (Tom van Stiphout) wrote in
<ri********************************@4ax.com>:

It's a very good idea to be current on Jet service packs. Jet4SP8
is the latest version.

And you should use either 6 or 8, not 7, which was a bugfest (8 is
just the bug fix for 7).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Tony Toews]

"Mark" <he******@yahoo.com> wrote:

(Sorry for the delay. ISP not processing outbound messages for a few days.)

Thanks for your help but the changes you mentioned did not help.

The registry setting was added on the server side and all the client
machines already have service pack 3. We had a total of 5 corruption's today
in 2 different databases.
Interesting. The OpLocks setting is definitely the first thing to check with a new
server.
We had a rep. from Microsoft on the phone today and he thinks that it is not
Ops Locks that is the problem. He told us that the MSJET DLL that we are
using is old but this is the same DLL we used in the Win NT server
environment with no corruption's. We made the change this evening with the
DLL and just have to pray that it works. Microsoft told us to try this
first and if it does not work to call them back. Do you think they know what
they are talking about? If anyone has any insight to this type of problem
please by all means help us out. I guess if all else fails we can go back to
the Win NT server were we had no corruption's but eventually we have to
upgrade.

What MSJet DLL and where does it reside? Presumably on all the client systems. And
not on the server. There is no need to install any Jet DLLs on the server as
Access running on the client workstations wouldn't use them.

Have you folks split the databases into a FE/BE with each user getting their own copy
of the FE?

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

[Tony Toews]

dX********@bway.net.invalid (David W. Fenton) wrote:

Are the Access installations at least SR1a+ and at least Jet
4 Service Pack 6? If not, you'll continue to experience corruption.
Once you have that in place in 100% of workstations (even one out
of 100 will cause corruption), the you can start looking at other
sources of problems.
Agreed that one workstation with a different Jet SP level can cause corruptions.
And don't just guess -- check every single workstation.
I know David knows this but I thought I'd add the following which has a link to code
for the benefit of the original poster and the lurkers.

What I've done is use the various API calls available and am checking the version
number and date/time of a crucial dll, msjetxx.dll, to ensure it matches what I have
on my system. See the tips page at my website for more details including sample
code: Verify Appropriate Jet Service Pack is installed
www.granite.ab.ca\access\verifyjetsp.htm

I should likely be a bit more redundant and check every file distributed by the Jet
SP.
At my
largest installation (about 40 workstations) I put in code that
logs Access version and Jet version in a central table when the
users log in so I can always check who is running what version of
Access (and, yes, workstations revert when they are rebuilt by
techs who don't know what they need to do to fully re-install
Access).

Absolutely agreed. This is now standard practice for me whenever I do something new
or renovate an already existing app.

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

[Tony Toews]

dX********@bway.net.invalid (David W. Fenton) wrote:

And you should use either 6 or 8, not 7, which was a bugfest (8 is
just the bug fix for 7).

Jet 4.0 SP8 also has the sandbox mode, etc, for better security which SP7 didn't.
SP7 was only out for what seemed to be three or four weeks before SP8 came out.
Dunno why they even bothered with SP7.

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

[Red]

"Tony Toews"

Jet 4.0 SP8 also has the sandbox mode, etc, for better security which SP7

didn't.

What's sandbox mode?
Can you post a link to kb or MSDN for details?

Bye: Red

[David W. Fenton]

tt****@telusplanet.net (Tony Toews) wrote in
<ie********************************@4ax.com>:

dX********@bway.net.invalid (David W. Fenton) wrote:

And you should use either 6 or 8, not 7, which was a bugfest (8
is just the bug fix for 7).

Jet 4.0 SP8 also has the sandbox mode, etc, for better security
which SP7 didn't. SP7 was only out for what seemed to be three or
four weeks before SP8 came out. Dunno why they even bothered with
SP7.

Actually, SP7 was out long before that, when the documentation web
page said it was applicable only to the beta of Access 2003.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Tony Toews]

dX********@bway.net.invalid (David W. Fenton) wrote:

Actually, SP7 was out long before that, when the documentation web
page said it was applicable only to the beta of Access 2003.

Hmm, "I have no recollection". <smile>

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

[Tony Toews]

"Red" <xx**@usa.net> wrote:

What's sandbox mode?
Can you post a link to kb or MSDN for details?

http://support.microsoft.com/default...b;en-us;294698

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

[Mark]

HELP!

We have now made sure every user is running msjet40.dll service pack 8 as
well as ops locks registry setting added to the server. All users are
running windows 2000 with service pack 3 installed. After all this and we
are still experiencing corruption's. The corruption's usually start around
12:00 PM when database traffic gets heavier. As was stated before we never
experienced this problem before when we were running Win 2K service pack 3
on the Win NT server. Any more suggestions.
Regards,
Mark
he******@yahoo.com

"Tony Toews" <tt****@telusplanet.net> wrote in message
news:j1********************************@4ax.com...

"Mark" <he******@yahoo.com> wrote:

(Sorry for the delay. ISP not processing outbound messages for a few days.)

Thanks for your help but the changes you mentioned did not help.

The registry setting was added on the server side and all the client
machines already have service pack 3. We had a total of 5 corruption's todayin 2 different databases.
Interesting. The OpLocks setting is definitely the first thing to check

with a new server.

We had a rep. from Microsoft on the phone today and he thinks that it is notOps Locks that is the problem. He told us that the MSJET DLL that we are
using is old but this is the same DLL we used in the Win NT server
environment with no corruption's. We made the change this evening with theDLL and just have to pray that it works. Microsoft told us to try this
first and if it does not work to call them back. Do you think they know whatthey are talking about? If anyone has any insight to this type of problem
please by all means help us out. I guess if all else fails we can go back tothe Win NT server were we had no corruption's but eventually we have to
upgrade.
What MSJet DLL and where does it reside? Presumably on all the client

systems. And not on the server. There is no need to install any Jet DLLs on the server as Access running on the client workstations wouldn't use them.

Have you folks split the databases into a FE/BE with each user getting their own copy of the FE?

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

[James Neumann]

Mark,

Really dumb question - could you be running into issues caused by a
backup routine running on your server? We recently had a situation
somewhat similar to this that we traced to a backup that running while
users were still in the app. Yes, I know that shouldn't happen - but
when we changed the backup schedule, the problem went away. This was
a commercial app that we didn't have the source code for, but which is
Access-based. (In this case, we had users that are smart enough to
always log out!)

Also, have you checked that you don't have a flaky NIC card or bad
cabling? Access is quite sensitive to this. Given what you describe,
I don't think that is the case, but it might be worthwhile to
eliminate the possibility.

JCN
"Mark" <he******@yahoo.com> wrote in message news:<Nt********************@comcast.com>...

HELP!

We have now made sure every user is running msjet40.dll service pack 8 as
well as ops locks registry setting added to the server. All users are
running windows 2000 with service pack 3 installed. After all this and we
are still experiencing corruption's. The corruption's usually start around
12:00 PM when database traffic gets heavier. As was stated before we never
experienced this problem before when we were running Win 2K service pack 3
on the Win NT server. Any more suggestions.
Regards,
Mark
he******@yahoo.com

"Tony Toews" <tt****@telusplanet.net> wrote in message
news:j1********************************@4ax.com...

"Mark" <he******@yahoo.com> wrote:

(Sorry for the delay. ISP not processing outbound messages for a few

days.)

Thanks for your help but the changes you mentioned did not help.

The registry setting was added on the server side and all the client
machines already have service pack 3. We had a total of 5 corruption's todayin 2 different databases.

Interesting. The OpLocks setting is definitely the first thing to check

with a new

server.

We had a rep. from Microsoft on the phone today and he thinks that it is notOps Locks that is the problem. He told us that the MSJET DLL that we are
using is old but this is the same DLL we used in the Win NT server
environment with no corruption's. We made the change this evening with theDLL and just have to pray that it works. Microsoft told us to try this
first and if it does not work to call them back. Do you think they know whatthey are talking about? If anyone has any insight to this type of problem
please by all means help us out. I guess if all else fails we can go back tothe Win NT server were we had no corruption's but eventually we have to
upgrade.

What MSJet DLL and where does it reside? Presumably on all the client

systems. And

not on the server. There is no need to install any Jet DLLs on the

server as

Access running on the client workstations wouldn't use them.

Have you folks split the databases into a FE/BE with each user getting

their own copy

of the FE?

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

[Mark]

JCN,

We have 2 back ups that run on around 6:00 AM and one around 6:00 PM both
are when there are no users in the database. I don't think flaky NIC cards
are the cause here due it being the same users pretty much everyday that use
the databases. I have another conference call scheduled for tomorrow with
our server staff and Microsoft ,wish me luck. I am running out of ideas.

Mark
"James Neumann" <bo*********@hotmail.com> wrote in message
news:77*************************@posting.google.co m...

Mark,

Really dumb question - could you be running into issues caused by a
backup routine running on your server? We recently had a situation
somewhat similar to this that we traced to a backup that running while
users were still in the app. Yes, I know that shouldn't happen - but
when we changed the backup schedule, the problem went away. This was
a commercial app that we didn't have the source code for, but which is
Access-based. (In this case, we had users that are smart enough to
always log out!)

Also, have you checked that you don't have a flaky NIC card or bad
cabling? Access is quite sensitive to this. Given what you describe,
I don't think that is the case, but it might be worthwhile to
eliminate the possibility.

JCN
"Mark" <he******@yahoo.com> wrote in message

news:<Nt********************@comcast.com>...

HELP!

We have now made sure every user is running msjet40.dll service pack 8 as well as ops locks registry setting added to the server. All users are
running windows 2000 with service pack 3 installed. After all this and we are still experiencing corruption's. The corruption's usually start around 12:00 PM when database traffic gets heavier. As was stated before we never experienced this problem before when we were running Win 2K service pack 3 on the Win NT server. Any more suggestions.
Regards,
Mark
he******@yahoo.com

"Tony Toews" <tt****@telusplanet.net> wrote in message
news:j1********************************@4ax.com...

"Mark" <he******@yahoo.com> wrote:

(Sorry for the delay. ISP not processing outbound messages for a few

days.)

>Thanks for your help but the changes you mentioned did not help.
>
>The registry setting was added on the server side and all the client
>machines already have service pack 3. We had a total of 5 corruption's

today

>in 2 different databases.

Interesting. The OpLocks setting is definitely the first thing to

check with a new

server.

>We had a rep. from Microsoft on the phone today and he thinks that it

is not

>Ops Locks that is the problem. He told us that the MSJET DLL that we

are >using is old but this is the same DLL we used in the Win NT server
>environment with no corruption's. We made the change this evening with the

>DLL and just have to pray that it works. Microsoft told us to try

this >first and if it does not work to call them back. Do you think they know what

>they are talking about? If anyone has any insight to this type of

problem >please by all means help us out. I guess if all else fails we can go back to

>the Win NT server were we had no corruption's but eventually we have

to >upgrade.

What MSJet DLL and where does it reside? Presumably on all the client

systems. And

not on the server. There is no need to install any Jet DLLs on the

server as

Access running on the client workstations wouldn't use them.

Have you folks split the databases into a FE/BE with each user getting

their own copy

of the FE?

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

[James Neumann]

Mark,

Would you mind posting back with the resolution? I'm very curious.

JCN

"Mark" <he******@yahoo.com> wrote in message news:<__********************@comcast.com>...

JCN,

We have 2 back ups that run on around 6:00 AM and one around 6:00 PM both
are when there are no users in the database. I don't think flaky NIC cards
are the cause here due it being the same users pretty much everyday that use
the databases. I have another conference call scheduled for tomorrow with
our server staff and Microsoft ,wish me luck. I am running out of ideas.

Mark
"James Neumann" <bo*********@hotmail.com> wrote in message
news:77*************************@posting.google.co m...

Mark,

Really dumb question - could you be running into issues caused by a
backup routine running on your server? We recently had a situation
somewhat similar to this that we traced to a backup that running while
users were still in the app. Yes, I know that shouldn't happen - but
when we changed the backup schedule, the problem went away. This was
a commercial app that we didn't have the source code for, but which is
Access-based. (In this case, we had users that are smart enough to
always log out!)

Also, have you checked that you don't have a flaky NIC card or bad
cabling? Access is quite sensitive to this. Given what you describe,
I don't think that is the case, but it might be worthwhile to
eliminate the possibility.

JCN
"Mark" <he******@yahoo.com> wrote in message

news:<Nt********************@comcast.com>...

HELP!

We have now made sure every user is running msjet40.dll service pack 8 as well as ops locks registry setting added to the server. All users are
running windows 2000 with service pack 3 installed. After all this and we are still experiencing corruption's. The corruption's usually start around 12:00 PM when database traffic gets heavier. As was stated before we never experienced this problem before when we were running Win 2K service pack 3 on the Win NT server. Any more suggestions.
Regards,
Mark
he******@yahoo.com

"Tony Toews" <tt****@telusplanet.net> wrote in message
news:j1********************************@4ax.com...
> "Mark" <he******@yahoo.com> wrote:
>
> (Sorry for the delay. ISP not processing outbound messages for a few days.) >
> >Thanks for your help but the changes you mentioned did not help.
> >
> >The registry setting was added on the server side and all the client
> >machines already have service pack 3. We had a total of 5 corruption's
today > >in 2 different databases.
>
> Interesting. The OpLocks setting is definitely the first thing to check
with a new > server.
>
> >We had a rep. from Microsoft on the phone today and he thinks that it is
not > >Ops Locks that is the problem. He told us that the MSJET DLL that we are > >using is old but this is the same DLL we used in the Win NT server
> >environment with no corruption's. We made the change this evening with
the > >DLL and just have to pray that it works. Microsoft told us to try this > >first and if it does not work to call them back. Do you think they know
what > >they are talking about? If anyone has any insight to this type of problem > >please by all means help us out. I guess if all else fails we can go back
to > >the Win NT server were we had no corruption's but eventually we have to > >upgrade.
>
> What MSJet DLL and where does it reside? Presumably on all the client systems. And > not on the server. There is no need to install any Jet DLLs on the server as > Access running on the client workstations wouldn't use them.
>
> Have you folks split the databases into a FE/BE with each user getting their own copy > of the FE?
>
> 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

[Mark]

JCN,

Our conference call on Tuesday was with an Access developer for Microsoft.
He basically asked a bunch of questions about the databases that are getting
corrupted and told us that it sounds like they are soundly built. He
suggested the next step to be to loaded Service pack 4 for Win 2K on the
client and the server. It supposedly has more fixes for the Win 2K
redirector issues which he says are more of an issue with Access 2K then Ops
Locks. Unfortunately due to red tape at our company there is a chain of
command that we have to go through to get approval for Service Pack 4. We
may end up going back to the Win NT server in the meantime. The person from
Microsoft also made mention that if Service Pack 4 does not work we may have
to disable Ops Locks on all the client machines. THE SAGA CONTINUES......:(
Mark

"James Neumann" <bo*********@hotmail.com> wrote in message
news:77**************************@posting.google.c om...

Mark,

Would you mind posting back with the resolution? I'm very curious.

JCN

"Mark" <he******@yahoo.com> wrote in message

news:<__********************@comcast.com>...

JCN,

We have 2 back ups that run on around 6:00 AM and one around 6:00 PM both are when there are no users in the database. I don't think flaky NIC cards are the cause here due it being the same users pretty much everyday that use the databases. I have another conference call scheduled for tomorrow with our server staff and Microsoft ,wish me luck. I am running out of ideas.

Mark
"James Neumann" <bo*********@hotmail.com> wrote in message
news:77*************************@posting.google.co m...

Mark,

Really dumb question - could you be running into issues caused by a
backup routine running on your server? We recently had a situation
somewhat similar to this that we traced to a backup that running while
users were still in the app. Yes, I know that shouldn't happen - but
when we changed the backup schedule, the problem went away. This was
a commercial app that we didn't have the source code for, but which is
Access-based. (In this case, we had users that are smart enough to
always log out!)

Also, have you checked that you don't have a flaky NIC card or bad
cabling? Access is quite sensitive to this. Given what you describe,
I don't think that is the case, but it might be worthwhile to
eliminate the possibility.

JCN
"Mark" <he******@yahoo.com> wrote in message

news:<Nt********************@comcast.com>...

> HELP!
>
> We have now made sure every user is running msjet40.dll service pack 8

as

> well as ops locks registry setting added to the server. All users

are > running windows 2000 with service pack 3 installed. After all this and we

> are still experiencing corruption's. The corruption's usually start

around

> 12:00 PM when database traffic gets heavier. As was stated before we

never

> experienced this problem before when we were running Win 2K service

pack 3

> on the Win NT server. Any more suggestions.
>
>
> Regards,
> Mark
> he******@yahoo.com
>
>
>
> "Tony Toews" <tt****@telusplanet.net> wrote in message
> news:j1********************************@4ax.com...
> > "Mark" <he******@yahoo.com> wrote:
> >
> > (Sorry for the delay. ISP not processing outbound messages for a

few days.)

> >
> > >Thanks for your help but the changes you mentioned did not help.
> > >
> > >The registry setting was added on the server side and all the

client > > >machines already have service pack 3. We had a total of 5

corruption's
today

> > >in 2 different databases.
> >
> > Interesting. The OpLocks setting is definitely the first thing to check
with a new

> > server.
> >
> > >We had a rep. from Microsoft on the phone today and he thinks

that it is
not

> > >Ops Locks that is the problem. He told us that the MSJET DLL that

we are

> > >using is old but this is the same DLL we used in the Win NT

server > > >environment with no corruption's. We made the change this evening

with
the

> > >DLL and just have to pray that it works. Microsoft told us to

try this

> > >first and if it does not work to call them back. Do you think

they know
what

> > >they are talking about? If anyone has any insight to this type of

problem

> > >please by all means help us out. I guess if all else fails we can

go back
to

> > >the Win NT server were we had no corruption's but eventually we

have to

> > >upgrade.
> >
> > What MSJet DLL and where does it reside? Presumably on all the

client systems. And

> > not on the server. There is no need to install any Jet DLLs on

the server as

> > Access running on the client workstations wouldn't use them.
> >
> > Have you folks split the databases into a FE/BE with each user

getting their own copy

> > of the FE?
> >
> > 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