> # Error Handling

> The following types of errors can occur when you are using the SequeLink for ADO Client:

> - SequeLink for ADO data provider errors
> - SequeLink Client errors
> - SequeLink Server errors
> - Database errors

> ### SequeLink® for ADO Provider Errors

> An error generated by the SequeLink for ADO data provider has the following format:

>     [DataDirect] [SequeLink ADO provider] message

> For example:

>     [DataDirect] [SequeLink ADO provider] Invalid precision
>     specified.

> The native error code is always zero (0).

> If you receive this type of error, check the last ADO call your application made. Contact your ADO or OLE DB application vendor, or refer to the ADO and OLE DB documentation available from Microsoft.

> ### SequeLink® Client Errors

> An error generated by the SequeLink for ADO Client has the following format:

>     [DataDirect] [SequeLink ADO provider] [SequeLink Client]
>     message

> For example:

>     [DataDirect] [SequeLink ADO provider] [SequeLink Client]
>     Memory allocation error occurred.

> Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, refer to the SequeLink Troubleshooting Guide and Reference.

> ### SequeLink® Server Errors

> An error generated by SequeLink Server has the following format:

>     [DataDirect] [SequeLink ADO provider] [SequeLink Server]
>     message

> For example:

>     [DataDirect] [SequeLink ADO provider] [SequeLink Server]
>     Only Select statements are allowed in this read-only
>     connection.

> Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, refer to the SequeLink Troubleshooting Guide and Reference.

> ### Database Errors

> An error generated by the database has the following format:

>     [DataDirect] [SequeLink ADO provider] [...] message

> For example:

>     [DataDirect] [SequeLink ADO provider] [Oracle]
>     ORA-00942:table or view does not exist.

> Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.