1) Why #1/24/2004# date on null time fields?
2) I am looking into the UTC issue with date fields and this may just be a best pratice issue. Would you put the time shift in the SQL statement or would you wait till the databinding events? I have limited experience with SQL so I haven't a clue if it could/should/would be done SQL.
3) This may be esoteric but what would be good practice using the SDK when binding date, datetime and time fields. A generic Object as in the first example or a nullable date as in the second? I prefer nullable date? but if the time field ever changes to anything other then the sudo datetime it is today, say timeSpan; nullable date? would break.
Public Property DateValue() As Object
Me.Value = value
-- Jim durkin