× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. June 2009

RE: TIMESTAMP type interpreted as char by OleDb - Fixed THANKS!



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Tom Deskevich
Sent: Thursday, June 04, 2009 7:33 AM
To: 'RPG programming on the IBM i / System i'
Subject: RE: TIMESTAMP type interpreted as char by OleDb - Fixed
THANKS!

That did the trick! The connection properties default was to convert
the
time to a string.
God Bless your children's children's children...

Just be aware that the reason this is an optional value in the connection
properties is because there is a loss of precision when going from a DB2
Timestamp to a DateTime value in the .NET framework. This could create
problems if you read in a DB2 record, change a few columns unrelated to the
Timestamp column, and then save the whole record back.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.