Hi,
I need to trap a possible error when I am inserting into a linked server. I have a linked server which is just an access database which a stored procedure copies records into out from SQL server.
This is done at night and the stored procedure is called from access code using ADO so it is important that any possible error does not cause the code to stop because it will not be picked up until the following morning.
I have trapped all the errors concerning inserts etc but is there anyway to trap the possiblity that the access file could have been removed or is unavailable?
If this is the case at the moment, it causes my VB to stop.
Thanks for any help,
Mark.
I need to trap a possible error when I am inserting into a linked server. I have a linked server which is just an access database which a stored procedure copies records into out from SQL server.
This is done at night and the stored procedure is called from access code using ADO so it is important that any possible error does not cause the code to stop because it will not be picked up until the following morning.
I have trapped all the errors concerning inserts etc but is there anyway to trap the possiblity that the access file could have been removed or is unavailable?
If this is the case at the moment, it causes my VB to stop.
Thanks for any help,
Mark.