devinemke;10912932 wrote:i assume you are using a RDBMS to store the calendar data. furthermore i will assume that each event is a record in that database. i will assume even further that each event record has a field for the start date/time and another for end date/time. if these assumptions are correct then what is the problem? an event could easily start on one day and end on another. for example:
start: 2009-04-29 11:27:12
end: 2009-05-05 16:34:59
Thank you for your reply.
You are correct in thinking that I have an events table within a database, which has a number of columns, including start date, start time, end date, end time, etc.
Storing and retrieving the information is not a problem.
For example, let's say an event starts on 01/04/2009 and ends on 05/04/2009. I would like to show that information literately and visually spanning over those days.
Should I display my calendar as a table and some how use a number of cells which span the required number of columns? Is it worth layering each event?
Please see attached example for better understanding.
Hope this helps.