J
J M
Hi,
I have a huge problem in an app I'm writing.
I use an OleDbDataset (and OleDbDataTable, and so on, created in the
Component Designer) to add rows to a table.
Three of the columns have Date/Time values.
Column 1 is only a date (time: 0:00), no problem there.
Columns 2&3 are only time (I struggled to extract only the time from a Date,
who the hell came up with the idea of returning the TimeOfDay prop of a
DateTime as a TimeSpan instead of a Date??)
Here comes the problem: In my DataRow object, all data is correct (checked
in QuickWatch), but in my database, the time columns are set to January 1,
2001 0:00.
I tried (among lots of other things, to test if I was doing something wrong)
to pass the literal #5/10/2004 15:32# in one of the columns. in the database
it showed as 5/10/2004 0:00...
When reading dates from existing (that is, data that was already in the
database before, entered in Access), there seems to be no problem....
J Mous
I have a huge problem in an app I'm writing.
I use an OleDbDataset (and OleDbDataTable, and so on, created in the
Component Designer) to add rows to a table.
Three of the columns have Date/Time values.
Column 1 is only a date (time: 0:00), no problem there.
Columns 2&3 are only time (I struggled to extract only the time from a Date,
who the hell came up with the idea of returning the TimeOfDay prop of a
DateTime as a TimeSpan instead of a Date??)
Here comes the problem: In my DataRow object, all data is correct (checked
in QuickWatch), but in my database, the time columns are set to January 1,
2001 0:00.
I tried (among lots of other things, to test if I was doing something wrong)
to pass the literal #5/10/2004 15:32# in one of the columns. in the database
it showed as 5/10/2004 0:00...
When reading dates from existing (that is, data that was already in the
database before, entered in Access), there seems to be no problem....
J Mous