Paul Hartland
paul.hartland at googlemail.com
Tue Mar 25 14:14:48 CDT 2014
We used to schedule employees work for up to 7 weeks in advance, so you would have a week row in tblAssigned for each employee, and have a little background function that would constantly ensure that there were at least 7 weeks of scheduling available for each employee. You could probably add another task called Swap, then the child or yourself in the first instance could change the code to Swap and when either of the other children open the app there could be an alert that says Child X needs to swap a task on Day X, with yes and not buttons, if the child clicks yes then swap the codes for that child on that day, you will have to think about if a child wants to swap, but neither of the others want to. Paul On 25 March 2014 18:59, David McAfee <davidmcafee at gmail.com> wrote: > I like this design idea, but it looks like I would have to be constantly > planning out the schedule. > > Maybe I can whip out the schedule for 3 months at a time. > > I'm actually going to use either a web front end (HTML5 & JQuery Mobile) > or (iPhone & Android) app based FE and a web based SQL Server BE, but I > will do the initial design in Access since it is so easy to kick stuff out > quickly. > > > I'm thinking that a way to simplify it right now is to not allow trading of > days, but I'd still like to plan for it. > > Maybe the ability for a user to select someone else for a certain job > number and if the other person agrees, the task is switched to them. > > That way I am not also dealing with what other day/task has to match to the > traded task. > > > > > On Tue, Mar 25, 2014 at 11:01 AM, Paul Hartland < > paul.hartland at googlemail.com> wrote: > > > David, > > > > As for everything (usually) you can make this quite simple or it could > > become a lot more complex, I used to work for a company where we assigned > > people to jobs, and this in it's simple form was based around three > tables, > > something like you have already thought of > > > > tblJobs > > JobNumber (int) JobType (nvarchar(50)) > > 1 Dishes > > 2 Trash > > 3 Free > > > > tblEmployee > > EmployeeID (int) EmployeeName (nvarchar(75)) > > 1001 Child 1 > > 1002 Child 2 > > 1003 Child 3 > > > > tblAssigned > > EmployeeID (int) WeekCommencing (date/time) Mon (int) Tues (int) Wed > > (int) Thurs (int) Fri (int) Sat (int) Sun (int) > > 1001 24/03/2014 1 > > 2 1 3 3 2 3 > > 1002 24/03/2014 2 > > 1 3 1 2 3 3 > > 1003 24/03/2014 3 > > 3 2 2 1 1 3 > > > > Then have a form which allowed you to select the employee (or child in > your > > case), this would then show a grid using tblAssigned to show (x) amount > of > > weeks, then in each day there would be a code (in this example > JobNumber). > > This is a simplistic idea of how one of my companies scheduling worked, > > but just an idea for you. > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 25 March 2014 17:26, Bill Benson <bensonforums at gmail.com> wrote: > > > > > David, a trivial seeming (but not so trivial) systen. I don't quite see > > how > > > to implement the free week concept, they can't all take their free week > > at > > > same time. And what happens if there are more chores than children, how > > is > > > this scalable? You cannot create weeks. > > > > > > Thorny, I have tried already looking at it from a number of ways for > > about > > > 45 minutes and actually gave up. > > > > > > Could you think of a point based system, suppose trash is lighter work > > than > > > dishes, gets a value of 5 and dishes 10. The goal is to hit a certain > > > number of points before earning a free week. But even this is hard to > > > scale: how do you ensure accountability (record and respond to defects > > and > > > half done chores), facilitate trading, add seasonal work. Worse, I > STILL > > > had the problem when more than one kid wanted to use their free week or > > > banked more than one. So free weeks ought to be pre assigned, but how > is > > > that gonna fit with everyone's busy schedule? > > > > > > Good Luck! , it will be interesting to see how simple and elegant > others' > > > solutions can be. > > > > > > On Mar 25, 2014 12:16 PM, "David McAfee" <davidmcafee at gmail.com> > wrote: > > > > > > > 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 > > > > > > > > > > > -- > > Paul Hartland > > paul.hartland at googlemail.com > > -- > > 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 > -- Paul Hartland paul.hartland at googlemail.com