I believe, there are not so many errors "related to connection issue" (though perhaps I do not understand what do you mean here exactly, connection is busy, connection name is invalid, ...).
I believe, you can create an utility table containing those errors (numbers and descriptions) of your choice, and look into this table when having aerror()>0.
>Hi Yuri,
>
>I believe you mean that I need to check the error and determine whether it is related to connection issue. How can I do that? To check through every single ODBC error and understand whether it is connection issue is quite a task.
>
>
>Thank you for your help.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only