[AccessD] A2003: Disk or Network Error

Darren,

  One of the things I've found in the past that has caused problems are
machines loaded with a NIC dialog protocol.  3COM was one of the first to
use this.

  What happens when this type of protocol is loaded is that the NIC is
disconnected from the network for a short time, diags are run, and then it's
reconnected.  The time is so short most apps don't notice, but JET does.

  I've also seen in the past where when more then one protocol is loaded,
timeouts can occur if the client and server are not using the same default
protocol.  This hasn't been a problem in recent years as almost everything
is standardized on TCP/IP, but it's worth mentioning.

  Check the network properties and see if anything other then the TCP/IP
Protocol is loaded. If a diag protocol is in there, get rid of it. 

  Beyond that, any type of network error can cause those issues (bad cable,
router, NIC, etc).  Also, one other thing I've seen that can cause these; a
TMP and/or TEMP environment variable that exists, but does not point to a
valid path or one that is not available.   Pretty rare now a days but again,
something worth mentioning.

HTH,
Jim.




-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darren D
Sent: Tuesday, September 30, 2008 7:49 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] A2003: Disk or Network Error

Hi Team

 

Apologies if I have asked this before

 

I have a dB that speaks with the BE. That BE that sits on a machine here
used as
a file share/server (It's not running Server software - just XP)

 

Quite often I'll leave for the night with my Access app happily displaying
its
main page only to return to a zillion "Disk or Network Error" message boxes
in
the morning

 

Obviously some time during the night the FE and BE have lost contact with
each
other - not too big a deal but I have to click through all the error
messages -
there can be up to 50 of them 

 

Then I have to re-boot the app - this is sometimes done un-gracefully from
the
task manager 

 

Is there a way I can trap this error at a dB kind of level - not a form
level -
then I can gracefully shut the app or alert the user to graceful shut the
app?

 

I think I know the error message number - just not sure where to trap for it

 

Many thanks

 

Darren

 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com