T
Tim Doe
We have recently installed a new server running Windows
2000 SP4. All clients on our small LAN are running
Windows 2000 SP2. We run an Access 2000 application
across the network with clients running the run-time .mde
that looks at a large (250 MB) .mdb on the server. All
worked fine until we put the data on the new server. Now
every workststion drops the network connection at least
once soon after startup, but then "settles down" and works
OK for the rest of the day. Does anyone know if there is a
Windows 2000 SP 2/4 conflict that causes the network
connection to drop or is it something to do with the
different versions of the MS Jet 4.0 Engine (although
there is no processing done on the server)? We have
another server on the network and the Access Application
appears to run fine on this (Windows 2000 SP 3).
Opportunistic record locking has not been changed from
default (ie allowed) on either server.
Anyone seen this sort of behaviour or have any ideas?
Any Ideas
2000 SP4. All clients on our small LAN are running
Windows 2000 SP2. We run an Access 2000 application
across the network with clients running the run-time .mde
that looks at a large (250 MB) .mdb on the server. All
worked fine until we put the data on the new server. Now
every workststion drops the network connection at least
once soon after startup, but then "settles down" and works
OK for the rest of the day. Does anyone know if there is a
Windows 2000 SP 2/4 conflict that causes the network
connection to drop or is it something to do with the
different versions of the MS Jet 4.0 Engine (although
there is no processing done on the server)? We have
another server on the network and the Access Application
appears to run fine on this (Windows 2000 SP 3).
Opportunistic record locking has not been changed from
default (ie allowed) on either server.
Anyone seen this sort of behaviour or have any ideas?
Any Ideas