> # Error Handling

> The following types of errors can occur when you are using the ODBC Client:

> - ODBC driver errors
> - SequeLink Client errors
> - SequeLink Server errors
> - Database errors

> ### SequeLink® for ODBC Driver Errors

> An error generated by the ODBC driver has the following format:

>     [DataDirect] [ODBC SequeLink driver] message

> For example:

>     [DataDirect] [ODBC SequeLink driver] Invalid precision
>     specified.

> If you receive this type of error, check the last ODBC call your application made. Contact your ODBC application vendor, or refer to the ODBC documentation included in the ODBC SDK.

> ### SequeLink® Client Errors

> An error generated by the ODBC Client has the following format:

>     [DataDirect] [ODBC SequeLink driver] [SequeLink Client]
>     message

> For example:

>     [DataDirect] [ODBC SequeLink driver] [SequeLink Client] The
>     specified transliteration module is not found.

> Use the native error code to look up details about the possible cause of the error.

> ### SequeLink® Server Errors

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

>     [DataDirect] [ODBC SequeLink driver] [SequeLink Server]
>     message

> For example:

>     [DataDirect] [ODBC SequeLink driver] [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.

> ### Database Errors

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

>     [DataDirect] [ODBC SequeLink driver] [...] message

> For example:

>     [DataDirect] [ODBC SequeLink driver] [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.