|
-
Nov 16th, 2000, 06:16 AM
#1
Thread Starter
New Member
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'.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|