[AccessD] A2003: Disk or Network Error

As it's already been mentioned, you should look into an underlying cause
for the disconnection, though there may be legitimate reasons why it is
disconnecting.  Depending how backups are run, some backup processes
will 'kill' access to a file, or even temporarily disconnect a
'session'.

If you are getting repeated 'Disk or Network Error' messages, it sounds
like the session is being disconnected.  It's a common network issue
with Access, that if you open up a database, with linked tables,
everything will be fine until you try to connect to a table where it
doesn't 'exist' network wise.  Even if the network returns, Access won't
'reconnect'.  It's one of my personal pet peeves with Access.

However, there is a better way to work around this.  You can do a simple
'if Dir("\\server\share\pathtodb\db.mdb")<>"" then' line to determine if
that .mdb is visible.  If you have linked tables, and kill your network
connection, nothing will happen UNTIL you try to use those linked
tables.  So, if you have an app running overnight, if you 'test' your
connection before you run something using those linked tables, you can
just 'fail over' if it doesn't see the remote .mdb.  

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darren D
Sent: Tuesday, September 30, 2008 6: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
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.