Elpidoforos
New member
- Local time
- Today, 10:25
- Joined
- Jan 24, 2014
- Messages
- 5
Hello and good day to all.
I am creating a database that's used for scheduling events. I've used Allen Browne's sample database as a starting point for creating recurring events.
see: allen browne website /apprecur
I've added some SQL to also be able to schedule events every 1st, 2nd, 3rd or 4th monday or tuesday of the month etc.
These are the problems I've encountered so far:
1.
because the event dates are calculated on the fly I do not understand how to best save history of a particular event in case of changes made to the main (not instance of) event.
In my database I want to link employee's to events and I want to be able to calculate work times. now if I decide to assign another employee all historic data is lost and the newly assigned employee seems to have suddenly worked many many hours already while the previously assigned one has lost all his hours.
2. how can I possibly prevent clashes/conflicts in recurring events?
Let's say we have two events we want to schedule, both want to make use of conference room 109. The one event starts on a monday and is repeated every 7 days and another event is scheduled to take place every 4th monday of the month.
how can I schedule in both of these events and prevent getting conflicts or how do I make those potential conflicts visible as soon as I enter the values for a new event?
is it possible to perhaps prioritize one event over another?
Thanks for looking at my questions, I appreciate all the help I can get!
Greetings Elpi
I am creating a database that's used for scheduling events. I've used Allen Browne's sample database as a starting point for creating recurring events.
see: allen browne website /apprecur
I've added some SQL to also be able to schedule events every 1st, 2nd, 3rd or 4th monday or tuesday of the month etc.
These are the problems I've encountered so far:
1.
because the event dates are calculated on the fly I do not understand how to best save history of a particular event in case of changes made to the main (not instance of) event.
In my database I want to link employee's to events and I want to be able to calculate work times. now if I decide to assign another employee all historic data is lost and the newly assigned employee seems to have suddenly worked many many hours already while the previously assigned one has lost all his hours.
2. how can I possibly prevent clashes/conflicts in recurring events?
Let's say we have two events we want to schedule, both want to make use of conference room 109. The one event starts on a monday and is repeated every 7 days and another event is scheduled to take place every 4th monday of the month.
how can I schedule in both of these events and prevent getting conflicts or how do I make those potential conflicts visible as soon as I enter the values for a new event?
is it possible to perhaps prioritize one event over another?
Thanks for looking at my questions, I appreciate all the help I can get!
Greetings Elpi
Last edited: