Main   Products   Offshore Outsourcing   Customers   Partners   ContactUs  
JDBC Databases
  HXTT Access 7.1.137
  Buy Now
  HXTT Cobol 5.0.137
  HXTT DBF 7.1.138
  HXTT Excel 6.1.141
  HXTT Json 1.0.109
  HXTT Paradox 7.1.137
  HXTT PDF 2.0.137
  HXTT Text(CSV) 7.1.137
  HXTT Word 1.1.137
  HXTT XML 4.0.138
Offshore Outsourcing
Free Resources
  Firewall Tunneling
  Search Indexing Robot
  Conditional Compilation
  Password Recovery for MS Access
  Password Recovery for Corel Paradox
  Checksum Tool for MD5
  Character Set Converter
  Pyramid - Poker of ZYH
Heng Xing Tian Tai Lab of Xi'an City (abbr, HXTT)

DST issue
Laura Irimiciuc
2010-07-26 06:44:26.0
When using bulk insert from sqlserver to access (accesspstmt.setObject(1, sqlserverRs)) with also setting timezone property to GMT on access connection ( props.setProperty("timezone", "local")) we noticed that 2010-03-14 02:00:00 is exported with one extra hour (2010-03-14 03:00:00 ).
The JVM's timezone is (UTC-05:00) Eastern Time (US & Canada) but I was assuming it won;t matter since i set GMT on connection props.
Is there a workaround for this issue?

Re:DST issue
HXTT Support
2010-07-26 08:13:29.0
>but I was assuming it won;t matter since i set GMT on connection props.
For GMT, you should use props.setProperty("timezone", "GMT")
Re:Re:DST issue
Laura Irimiciuc
2010-07-26 09:12:02.0
From a previous post, I was advised to use local...
Here is the link
Re:Re:Re:DST issue
HXTT Support
2010-07-26 17:50:07.0
Maybe it's resulted by SQL Server's time zone offset. You can try props.setProperty("timezone", "GMT-6")

Search Key   Search by Last 50 Questions


Copyright © 2003-2019 Heng Xing Tian Tai Lab of Xi'an City. | All Rights Reserved. | Privacy | Legal | Sitemap