IainMc2013
New member
- Local time
- Yesterday, 23:08
- Joined
- Apr 1, 2013
- Messages
- 7
I am creating a database in Access 2000 that includes managing weekly schedules that are divided into time slots each of 15 minutes. The only thing I need the time slots table to do is identify whether each time slot has been reserved or not.
There are two options I am considering for the structure of this table:
1. A field for the date and fields for each of the time slots so the table header will look like:
Date | Slot 2 | Slot 3 | Slot 4| Slot 5|............|Slot 64
and so on up to a total of 64 slots over 16 hours so there would be a single record for each day
2. A field for dates and a numeric field for time slots, using both of these to create a composite key in order to prevent duplication.
I am leaning towards the first option as this will only create up to 365 records for the entire year but I am wondering which of these options will use up less resources and allow for faster querying. In the first option a record would exist for every time slot but in the second only for those that have been allocated (probably using SQL and/or VB to determine that a slot has not been reserved).
In terms of how much I need the database to cope with, I am anticipating a 3-4 year lifetime for the application and of course past record could be purged from the database periodically.
Which would be the best structure to use for this table?
There are two options I am considering for the structure of this table:
1. A field for the date and fields for each of the time slots so the table header will look like:
Date | Slot 2 | Slot 3 | Slot 4| Slot 5|............|Slot 64
and so on up to a total of 64 slots over 16 hours so there would be a single record for each day
2. A field for dates and a numeric field for time slots, using both of these to create a composite key in order to prevent duplication.
I am leaning towards the first option as this will only create up to 365 records for the entire year but I am wondering which of these options will use up less resources and allow for faster querying. In the first option a record would exist for every time slot but in the second only for those that have been allocated (probably using SQL and/or VB to determine that a slot has not been reserved).
In terms of how much I need the database to cope with, I am anticipating a 3-4 year lifetime for the application and of course past record could be purged from the database periodically.
Which would be the best structure to use for this table?
