On Fri, 19 Sep 2008 08:09:44 -0400, Zhuo Li wrote:
Thank you for your reply. I think that it is something to do with the
datetime field and the dataset. When the dataset tries to save a row to
the database, it compares its "Original data"of the row with what is in
the database. This comparison always result in difference in the
datetime field. If there were a simple solution, there would be
something in the dataset configuration to set the rule of comparing two
datetime values only upto second. Any idea?
I can describe a problem I had and perhaps that will help you.
DateTimePicker associated with field. Field was sometime null in the
database. When you picked a new row if (and only if) the field was null
the control got an is null exception and 'rejected' the change of
position. I worked around this by disconnecting the picker from the
database and manually setting it with an onchange event on the
datasource. Very clunky.
I don't get the second message, the difference between two dates is a
timespan. If they are different and you are changing them the database
does not care. If you want to make them null then the automatic
database build will create a method SetFeildNull() and it can be checked
with IsFieldNull().
Ken