[AccessD] Chore Schedule

Not all tasks are daily. That is why I went for points.
On Mar 25, 2014 1:46 PM, "Rocky Smolin" <rockysmolin at bchacc.com> wrote:

> David:
>
> I'd put free week as a task.  But actually, I'd have the calendar each day
> instead of by the week so in tblPersonTaskJunct there would be a record for
> each day/person/task combination.
>
> In the FE I'd have a function that assigns a person to a task for an entire
> week (actually you could have starting date and ending date - that would
> give you more flexibility).
>
> Then for trades of a day, the user could just change the name of the person
> on that day. Giving the original person on that task another day/task would
> be up to the user.
>
> Of course, everybody has to play by the rules and not go into the system
> and
> give all their tasks to someone else.
>
> But I'd keep the BE as simply as possible - atomic: like keep the values
> like date as days instead of weeks - and put all your 'business rules' in
> the front end.
>
> R
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David McAfee
> Sent: Tuesday, March 25, 2014 9:15 AM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Chore Schedule
>
> So, I'm playing around with the idea of making a database for a task/chore
> schedule for our 3 kids.
> Right now they rotate between dishes, trash (inside and taking it to the
> curb) and a free week.
>
> They all have busy schedules with school, work, extra curricular activities
> and whatever else they might have time for. So a need may arise for one
> person to "request" a trade of a day or the complete week for another
> person. The other person would, obviously, have to approve it.
>
> I having a bit of trouble coming up with the table schema.
>
> Obviously we would have a table of tasks/chores:
>
> tblTask
> TaskID (AN, PK, INT)
> Task (Varchar(25))
>
> Sould the Free week be listed as a task for simplicity?
>
>
> I also need a person talbe
> tblPerson
> PersonID
> Person
>
> Would a junction table handle it all?
> tblPersonTaskJunct
> PKID
> TaskID
> PersonID
> WeekNumber ? DayNumber?
>
> Would I need another table for the trades?
>
> Any ideas?
>
> Thanks,
> David
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>