Main   Products   Offshore Outsourcing   Customers   Partners   ContactUs  
JDBC Databases
  HXTT Access v6.0
  HXTT Cobol v3.0
  HXTT DBF v6.0
  HXTT Excel v5.0
  HXTT Paradox v6.0
 
  Buy Now
  Support
  Download
  Document
  FAQ
  HXTT Text(CSV) v6.0
  HXTT XML v2.0
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 Ltd. of Beijing City (abbr, HXTT)

HXTT Paradox
Question about milliseconds precission
Sergio
2016-06-02 08:23:56.0
Hi,

We have recently purchased your JDBC connector for Paradox database, it seems to work properly but I have a problem with milliseconds precission.

We have an integration with external application that uses Paradox and they have relationships between tables with datetime primary key fields. When I have to insert a row in the related table, first of all I read the row on primary table and then copy the value to insert into the related table, but unfortunately this new row is not related with the primary when I see the results on this external application.

A example datetime value recovered from database have this format '2015/05/07 20:55:59.328000000', it seems like the connector is not retrieving the complete precission of this datetime, I think the original data have precission on this 0 end values ('2015/05/07 20:55:59.328XXXXXX').

Can you help me?

Best Regards,

Sergio
Re:Question about milliseconds precission
HXTT Support
2016-06-02 08:49:59.0
A Paradox timestamp value should have a resolution of 1/500 seconds. You can send us a simple database sample so that we can check the difference.

Search Key   Search by Last 50 Questions




Google
 

Email: webmaster@hxtt.com
Copyright © 1999-2017 Heng Xing Tian Tai Ltd. of Beijing City. | All Rights Reserved. | Privacy | Legal | Sitemap