Results 1 to 5 of 5

Thread: Microsoft Access Database Design Question

  1. #1
    Join Date
    Sep 2007
    Beans
    221

    Microsoft Access Database Design Question

    I'm making this database for a non-profit organizations where volunteers can clock in and out. There interface is in Java and the database is Microsoft Acces.

    So what would be the best design to record hours each time they clock in and out and then be able to get hours for a week, month and yearly?

    I have a few ideas in my head but they all seem to get cumbersome if a lot data is entered.

  2. #2
    Join Date
    Nov 2006
    Location
    Jo'burg, South Africa
    Beans
    434
    Distro
    Ubuntu 11.10 Oneiric Ocelot

    Re: Microsoft Access Database Design Question

    Hi, You're asking a very general question for quite an involved task.
    It would be helpful if you give us some of the ideas.. or a spec If you have one.

    First you need to know what the functionality of the database/application is going to be (in detail) and then take steps to design the database and/or app front-end.

    Is there any reason you're not using an OSS database like MYSQL or Postgres?

    Cheers
    Rax

  3. #3
    Join Date
    Sep 2007
    Beans
    221

    Re: Microsoft Access Database Design Question

    I suggested using MySQL or PostregreSQL but the ppl who I am working with feel comfortable with Micrsoft Access *cough*Microsoft Junkies*cough*.

    I've designed the GUI for the application, just the database. For the application, the user has a login name which is there initials, and when they click login it or log out, it records the time and date when the person did so.

    For the staff, they are going to have option to few a volunteers hours for that week, a choosen month, a choosen year, and all total. Currently there is a table with other volunteer information such as phone, address, name, etc. I was thinking of making another table that corresponds with the primary key of the volunteer's information table, which will hold the the id, date worked, and hours worked on that day. But when I think about it, that seems to get cumbersome.

    With that, I'm lost on how many tables I have for it to be efficient.
    Last edited by Black Mage; January 2nd, 2008 at 09:53 PM.

  4. #4
    Join Date
    Jul 2007
    Beans
    Hidden!
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Microsoft Access Database Design Question

    There are just two tables needed:

    Person(p#,Initials)
    Work_time_slice(p#,start_date_and_time,stop_date_a nd_time)

    With p# in Work_time_slice referring to p# in Person.
    ch
    In Switzerland we make it other
    with apologies to Gerard Hoffnung


  5. #5
    Join Date
    Dec 2006
    Location
    Planet Earth
    Beans
    683
    Distro
    Ubuntu

    Lightbulb Re: Microsoft Access Database Design Question

    Quote Originally Posted by Black Mage View Post
    I'm making this database for a non-profit organizations where volunteers can clock in and out. There interface is in Java and the database is Microsoft Acces.

    So what would be the best design to record hours each time they clock in and out and then be able to get hours for a week, month and yearly?

    I have a few ideas in my head but they all seem to get cumbersome if a lot data is entered.

    You could easily build what you are trying to do, using php or perl and a mysql database.

    If it's a matter of the application running on MS Windows, then that's not a problem either.
    Mysql is available for numerous platforms, as is php and perl.

    zipperback
    Last edited by zipperback; January 2nd, 2008 at 09:53 PM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •