Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2007
    Posts
    6

    Unanswered: database Prof said project not normalized properly (was "Please help me!")

    I have worked very hard in a database course this semester using access.
    I have been working on a final project. However the database Prof said
    my project was not "normalized" correctly. He said that the
    Living Status from the Client table and the Availibility From the
    Volunteer_Availibility table should both be moved into new tables.
    I really do not see a point in doing this. Could someone please help me
    I would REALLY be greatful to anyone who could do this for me or give me
    some help. The file is attached below.
    Last edited by gvee; 12-20-07 at 08:07. Reason: Attachment removed

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    I have worked very hard in a database course this semester using access.
    I have been working on a final project.
    I suggest working a little harder.

    However the database Prof said my project was not "normalized" correctly. He said that the Living Status from the Client table and the Availibility From the Volunteer_Availibility table should both be moved into new tables
    You have your answer right there.

    I really do not see a point in doing this.
    The point of any normalisation is the same -- to eliminate redundancy. Just do as your professor suggests.

    Could someone please help me
    Seems to me your professor has already done that. The rest is up to you.

    I would REALLY be greatful to anyone who could do this for me
    Nope. Don't be lazy. The best way to help you is to force you to do it yourself so that you actually learn.

    or give me some help.
    Ok, here's what you should do: the Living Status from the Client table and the Availibility From the Volunteer_Availibility table should both be moved into new tables.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Not to be cruel but StarTrekker is correct. You need to understand the basics and the only way to do that is to struggle a bit with learning them.

    I may recommend getting the Developers Handbook by Ken Getz to help you get started.
    Last edited by pkstormy; 12-19-07 at 21:57.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  4. #4
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,434
    Provided Answers: 10
    I've removed the attachment because this is not (yet) a practical excercise - you need to sit down and discuss the matter.

    Why don't you explain a bit more about what your project is and (in detail) the entities (tables) and how each one relates to the other (one-to-many, etc).

    But, this is homework, so we're not doing it for you...

    ...But we will try as hard as you do to get this solved
    George
    Home | Blog

  5. #5
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Yup agree with George. Give us some info about where you are and how you got there. Funny thing is, without knowing any of this my first thought is "your prof is wrong" - but it is impossible to even guess with so little information.

    ...and I'll reiterate George's comment - you'll get no homework done for you but if you are prepared to put in the effort you might get the odd pointer

Posting Permissions

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