Interesting info on Sql Server 2k
I have taken over another application, separate from my complaints of Tuesday, where I have found something very interesting. There are a couple of places where Classic ADO recordsets are used for inserting and updating data. A couple of the fields that are being updated have fields where a time value is stored in the datatime field, but with no associated date. When I converted this to a SQL based insert / update, I was now getting the “1/1/1900” placed into these fields that were only suppossed to be storing the time, as I had assumed I would be getting with just the recordsets insert / update. Well, it appears that if you place “Dec 30, 1899” infront of the time entry, you will only have the time entry stored in the field. Found this by using Sql Profiler and seeing what has done with a recordset based insert. Pretty interesting piece of info. Why these folks have decided to separate the date and the time of the operation into separate fields, I have no idea.
Wally