Thanks in advance
The mixed network protocols can cause some difficulties as well. NetBeui is
notorios for "spraying" packets all over the place and increasing network
traffic. Unless there's an overwhelming reason not to, I'd recommend
switching everything to strictly TCP/IP.
"Tony" <aman...@udsmr.org> wrote in news:3c8798b9$1_3@cnews:
Also, if you are also running Paradox or the ap from the network move them local
and just share the data. If that does not solve the problems you will have to
tell us more about the environment.
HTH
Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits since
1982
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
Change the EnableOplocks section from a 1 to a 0. If you don't see this key,
add it.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Param
eters
Change the UseOpportunisticLocking section from a 1 to a 0. If you don't see
this key, add it.
You should then restart your system for the change to take effect.
--------------------
Luigi Caselli
Tony <aman...@udsmr.org> wrote in message news:3c8798b9$1_3@cnews...
Does changing these keys hose up the users of other applications?
Norb
"Luigi Caselli" <luigic...@iol.it> wrote in message
news:3c8a9dee_2@cnews...
I've seen this recommended in network newsgroups and other desktop
database newsgroups as a fixative for any high traffic
contention/corruption issues.
Norbert Eckert wrote...
> You know, I see this mentioned all the time and wonder what impact changing
> these keys has on non BDE applications. For example, what happens to any
> Visual Basic database apps that use the JET engine or ADO objects? What
> about any Access databases that are already in use on a server before the
> Paradox tables are added to it?
>
> Does changing these keys hose up the users of other applications?
--
Lorrin (filter the spam to reply)
______________________________________
news://pnews.thedbcommunity.com
http://www.thedbcommunity.com/support/
for Paradox® support
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
"Lorrin Moore" <mSoP...@0S1PdAeMsSiPgAnM.com> wrote in message
news:MPG.16f697115...@cnews.corel.com...
Lorrin Moore <mSoP...@0S1PdAeMsSiPgAnM.com> wrote in
news:MPG.16f697115...@cnews.corel.com:
> > I've seen [modifying the oplocks reg keys] recommended in
> > network newsgroups and other desktop database newsgroups
> > as a fixative for any high traffic contention/corruption issues.
To which Jeff Shoaf replied...
> I think op locks probably help on "server-based" software like
> client/server databases, Exchange servers, Lotus Notes servers, web
> servers, etc. But you really shouldn't be running any of those on your file
> server...
OK, there have to be some communication lines crossed here. I stated
that a pessimistic locking scheme (ie: disabling Opportunistic Locking)
is prescribed as a fixative for corruption. Oplocks will give speed over
integrity. I was not attempting to solve the problem of the slow multi-
user environment. I'm not sure if "help" in your first sentence refers
to speed or integrity.
---
Sorry for any confusion. I like to share, and since I'm often confused
myself, I often accidently share my confusion!
Lorrin Moore <mSoP...@S0P1AdPeSsPiAgMn.com> wrote in
news:MPG.16f724d69...@cnews.corel.com: