Trapping 'Disk or Network Error' Error

[dch3]

Is it possible to trap the 'Disk or Network Error' that's thrown when an
Access front end looses its connection to the back end? I'm thinking not, but
had to ask.

 

[Allen Browne]

You can use the Error event of the form to be notified of the error.

However, it's not something you can solve, so I'm not sure how useful that
is to you.

 

[dch3]

Basically if I could trap it, I'd shut the front end down. We've got one PC
connecting to the DB via wireless in the warehouse (yes I know another
antenna is going up and SQLServer is on the horizon). The user can be away
from his PC for extended periods of time and typically returns with 1,000
msgboxes waiting for responses when the connection is dropped.

The current belief is that the connection isn't as durable due to 1) the
metal shelving between the antenna and the PC, 2) there's no line-of-sight
and 3) the PC's cards aren't as durable as a laptop's. We've got another
antenna that has to go up that should eliminate the first two issues.

 

[Allen Browne]

Hmm: pretty good way to corrupt an Access database.

If you are experiencing corruptions, you might consider either replacing the
wireless connection with Ethernet cable, or else running the sessions in
Teminal Server/Citrix. At least that way it won't suffer from the
interrupted write that occurs when packets disappear.