santoshamb@yahoo.com (ben) wrote in message news:<56d498d9.0402122240.6c38e6be@posting.google.com>...
> I have the table:
>
> Create Table ServiceSched(
> [key] primary key NOT NULL,
> [starttime] datetime NOT NULL,
> [endtime] datetime NOT NULL)
>
> (sql might not be perfect)
>
> when I enter records manually using enterprise manager, I type
> something like "8:00" into the starttime field, and E.M. expands the
> time to "8:00:00 AM".
>
> if I use a sproc to enter times
>
> alter proc addSchedule(
> @inStartTime datetime,
> @inEndTime datetime)
>
> as
>
> INSERT INTO ServiceSched([StartTime],[EndTime])
> VALUES (@inStartTime,@inEndTime)
>
> return
>
> execute addSchedule('8:00', '9:00')
>
> and then I look in enterprise manager, it has expaned these to
> '1/1/1900 8:00:00 AM' and '1/1/1900 9:00:00 AM'
>
> why is this? does it make a difference? am I inserting times wrong via
> a stored procedure?
>
> thanks for the help,
>
> Ben

"ben" <santoshamb@yahoo.com> wrote in message
news:56d498d9.0402122240.6c38e6be@posting.google.com...
> I have the table:
>
> Create Table ServiceSched(
> [key] primary key NOT NULL,
> [starttime] datetime NOT NULL,
> [endtime] datetime NOT NULL)
>
> (sql might not be perfect)
>
> when I enter records manually using enterprise manager, I type
> something like "8:00" into the starttime field, and E.M. expands the
> time to "8:00:00 AM".
>
> if I use a sproc to enter times
>
> alter proc addSchedule(
> @inStartTime datetime,
> @inEndTime datetime)
>
> as
>
> INSERT INTO ServiceSched([StartTime],[EndTime])
> VALUES (@inStartTime,@inEndTime)
>
> return
>
> execute addSchedule('8:00', '9:00')
>
> and then I look in enterprise manager, it has expaned these to
> '1/1/1900 8:00:00 AM' and '1/1/1900 9:00:00 AM'
>
> why is this? does it make a difference? am I inserting times wrong via
> a stored procedure?
>
> thanks for the help,
>
> Ben