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...

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Alan Campin
Sent: Thursday, June 04, 2009 8:42 AM
To: RPG programming on the IBM i / System i
Subject: Re: TIMESTAMP type interpreted as char by OleDb


It is the default. It converts date and timestamp fields to Char. Look at
the properties for your OLEDB connection and you will find one where you can
tell it to leave the field as Date or Timestamp.

On Thu, Jun 4, 2009 at 5:47 AM, Tom Deskevich <
thomas.l.deskevich@xxxxxxxxxxxxx> wrote:

I created an SQL table using Systemi Navigator. I added a timestamp
type column.

When I read this table in via oledb to my vb.net project, it
interprets it as character.

Which does not allow any editing by Crystal reports when I report this
column.

Any idea why oledb interpreted a timestamp type column as char?
Thanks. I certainly am not asking for help with Crystal reports, but
just why this column is char.

Tom Deskevich
Infocon Corporation
Phone 814-472-6066
Fax 814-472-5019

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.