Losing your Network Connection to an SQL dB

What is the best way to handle the loss of your network connection to a remote dB. Putting in lots of 'If err.number =', seems a clumsy way of trapping all the errors. Does anyone know of a neater/cleaner way of buffering data when a connection fails and sending it when a connection is active again.
At present most of what I have is using RD02, Recordsets using EDIT and UPDATE on SQL 6.5 and 7.0 dBases, which works fine until I get a network 'Glitch'.

Could you use ADO and then submit batch updates?

The error handling in DAO/RDO/ADO is never going to be a thing of beauty, but I think the Err.Number approach is pretty much the only one you can take...

Cheers,

P.