• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Daily calendar for scheduling people

 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi friends,
Has anyone ever developed a calendar that could schedule people. For example, like a calendar used in doctor's offices. I am half way into developing this calendar, but I am stuck b/c I do not know how to schedule people, example
January 26, 2004
9:00 AM John Smith
10:00 Am Jack Jones
March, 15, 2004
10:00 AM Suzan Stone
11:00 AM John Rambone
But I need these names to be saved. So that when they go back and forth on the schedule, the names will be there. Can any one help?
I am sure some smart person out there has done this.
Thank you very much!
JM
[ January 26, 2004: Message edited by: Jim Martin ]
 
Ranch Hand
Posts: 276
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is your question an inquiry of how to save this data to a database table or a set of tables? Such as a recomendation of a database table design, or are you needing more help on the java side of things?
 
Jim Martin
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kim
Is your question an inquiry of how to save this data to a database table or a set of tables? Such as a recomendation of a database table design, or are you needing more help on the java side of things?
My problem is with the former. I do not need more help on the java side(I hope!). The part for the management of individual people (i.e. first name, last name, address, etc.) is done and every person's info. is saved in a database in an organized manner.
Yes, my problem is with saving this data to a database. But I was wondering, this schedule could get pretty big over the years. In fact, I think there is no other way than saving the information that is enetered into this calendar to some file or a database.
Have you ever done a somewhat complicated Calendar for scheduling people. Now these people are already availalbe in a database that is connected to this Java program.
I think I will probably end up opening another database, to save the people's name and their unique id number, so that when the user is going forward or backward, the program will update the page for the particular day that the user wants to look at. Then, make every cell in the table (calendar for that day), an action listener, so that when the user clicks on one of the cells, the entire information for that person scheduled and what the schedule is for is presented to the user.
What do you think? Have you ever done this?
Boy, just writing this response has given me some good ideas, thanks!
 
Kim Kantola
Ranch Hand
Posts: 276
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Jim, yes I happen to be working on a scheduler app as we speak. Its a bit differant than yours, we are scheduling employee's for shifts, but I think it would include a lot of the same tasks.
We do have a database that saves all the data about a person, in our case, an employee, this database contains an employeeId column.
We have another table called "WeeklySchedules" which saves the schedule start date, and a scheduleId.
Then another table saves "shifts" which in your case could be "appointments." This table shows the employeeId, the ScheduleId, and then a start and end time of the shift.
Having a separate Id for ScheduleId helps with reporting on all appointments for a specific week.
Hope this gives you more good idea's.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic