Troubleshooting > ThirdPartyIssues > Resolving Incorrect Time Zone Handling When Using ODBC

Resolving Incorrect Time Zone Handling When Using ODBC

Article #: Product: Version:

Summary

Some implementations of the Open Database Connectivity (ODBC) specification do not support date/time or timestamp columns containing time zone information. As a result, tasks that read from or write to such columns may behave unexpectedly when using ODBC. The time zone information is sometimes ignored, or you may encounter errors during task development or at run time.

This issue can be resolved in the following ways:

Symptom

When developing a task that accesses database tables via ODBC, columns with a data type such as "time with time zone" or "timestamp with time zone" may or may not appear as expected in the DMExpress Task Editor, and the associated time zone data may not be handled as expected at run time.

At design time, in the Source Database Table dialog of the DMExpress Task Editor, the column may:

At run time, the following may occur:

The behavior depends on the database management system and ODBC driver being used. To determine how time zone data is handled when using ODBC, refer to your database management system and ODBC driver documentation.

Resolution

There are several potential workarounds for this issue, some of which may be used in combination.

Last updated: