[thelist] New annoying feature of SQL Server

[Scott Dexter]

> -----Original Message-----
> From: Rob Smith [mailto:rob.smith at THERMON.com]

> ThaTime = Time
> ...   ...
> ...   1/1/1900 9:24:09 AM

SQL Server doesn't have a narrow "time" datatype, so it has to associate
a date with your value. It picks 1/1/1900 as default.

Why are you breaking up the values? You can store both in one field
(saving space), and then display as needed on output (as Rudy suggests)

sgd
--
TALX FasTime Services
Customized Systems for H.R., Payroll, and Employee Self Service
	*	Telephone/Internet Time and Attendance
	*	Telephone/Internet Surveys
	*	Automated Outbound Calling and Messages
http://www.ti3.com/TALX-Ti3/TALXTi3Fastime.htm