network disconnect solution

[Steve Jensen]

For years, through the many versions of Access, one thing seems to be
constant - in a front-end, back-end situation, if the network connection is
interrupted for even a nano-second, the front-end loses the connection to the
back end and cannot get it back. You see a lot of error 91 _object variable
not set, #error in table rows, etc. A restart of the application is
required. This is decidedly unfriendly to the end user.

It also makes Access applications almost unsupportable on a wireless LAN, as
wireless is notoriously hot and cold and subject to all sorts of
environmental issues, and doesn't have the performance of a wired network in
the best of conditions.

Is there some way of making the front-end reconnect when it encounters this
error without having to restart the app? Also, do any of the ODBC or DDE
settings have any affect on this?

 

[Chris O'C via AccessMonster.com]

The solution isn't to reconnect after a network disconnection, it's to put
Access on a stable network.

Never put an Access db on an unstable network, which a wireless LAN
definitely is. Network disconnections are the least of your problems. Db
corruption and data loss will be much bigger problems.

Chris
Microsoft MVP

 

[Steve Jensen]

I agree entirely. It is in our documentation, in fact. I just wondered if I
had missed something all these years.

 

[Chris O'C via AccessMonster.com]

You haven't missed anything. Access is still vulnerable to networks fumbling
the ball, even in Access 2007.

Chris
Microsoft MVP