Time Management App

[Stuart Ferguson]

I am currently writing a Time Management application which requires that
each weekday be split into morning, afternoon and evening (each with a
start and end time), i need to store these into a SQL Server database,
at the moment I am using a Stored Procedure to insert the data however
this requires 48 paramaters to send each individual start and end time
for each day and was wondering if there was a better way for this to be
done.

*** Sent via Developersdex http://www.developersdex.com ***

[SP]

"Stuart Ferguson" <st**************@btinternet.com> wrote in message
news:Od**************@TK2MSFTNGP15.phx.gbl...

I am currently writing a Time Management application which requires that
each weekday be split into morning, afternoon and evening (each with a
start and end time), i need to store these into a SQL Server database,
at the moment I am using a Stored Procedure to insert the data however
this requires 48 paramaters to send each individual start and end time
for each day and was wondering if there was a better way for this to be
done.

I am assuming you have 48 columns in your table. You should probably
normalize the table. What are the columns you currently have so we can give
you some suggestions?

SP

[Steve Walker]

In message <Od**************@TK2MSFTNGP15.phx.gbl>, Stuart Ferguson
<st**************@btinternet.com> writes

I am currently writing a Time Management application which requires that
each weekday be split into morning, afternoon and evening (each with a
start and end time), i need to store these into a SQL Server database,
at the moment I am using a Stored Procedure to insert the data however
this requires 48 paramaters to send each individual start and end time
for each day and was wondering if there was a better way for this to be
done.

http://rosca.net/writing/articles/xml_parameters.asp

--
Steve Walker