It's really going to be a function of what your user interface is -- you mentioned Excel, but then said it wasn't, and you also mentioned it's in a SQL table. I would assume that you'd use a 'date' field, so it's just a matter of dealing with the rest of it.The input date/time formats will be decided by myself. The excel is just where I have the initial list of times. I do apologize for mentioning it. The problem with the Excel file is 1; parsing it. And 2; data's not guarentee concistant. So to get around this limitation, I'm creating my own data storeage format for this. I'm debating on storing a time with each day of the week or doing some M-F type storage and parsing that out. All one line? Multiple lines, etc...
-- philip
We put the 'K' in kwality!
In reply to Re^2: Date/Time Parse with time exemptions and SQL querying
by guice
in thread Date/Time Parse with time exemptions and SQL querying
by guice
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |