Feedback
Did this article resolve your question/issue?

   

Article

Fetch from Salesforce BUSINESSHOURS table returns time in incorrect time zone

Information

 
TitleFetch from Salesforce BUSINESSHOURS table returns time in incorrect time zone
URL Namefetch-from-salesforce-businesshours-table-returns-time-in-incorrect-time-zone
Article Number000182207
EnvironmentProduct: Connect(64) XE for ODBC Salesforce driver
Version: 07.16.0218
OS: Windows
Database: Salesforce
Application: All supported applications
Question/Problem Description
Times are inserted into the BUSINESSHOURS table in America/New_York time zone. When the time is fetched, it is returned in UTC time zone. Times are shown in America/New_York time zone in the Salesforce GUI.
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberDefect 69674
Enhancement Number
Cause
The driver was using a different calendar when inserting and when fetching.
Resolution
Fixed in hot fix 07.16.0233.
Refer to article Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/20/2020 7:14 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.