Results 1 to 6 of 6

Thread: Database Idea

  1. #1
    Join Date
    Sep 2006
    Posts
    162

    Unanswered: Database Idea

    I need to make a database to track box number.
    They will be scanned into the system.
    Issued out to techs, then remove when they use them.

    I have a couple of ideas, but i'm trying to think of the best way to do it.

    Any pointers would help on how to structure it.

    TIA

  2. #2
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    What are your ideas so far Jay?
    Testimonial:
    pootle flump
    ur codings are working excelent.

  3. #3
    Join Date
    Sep 2006
    Posts
    162
    Have a couple of tables.
    Boxs in warehouse.
    Boxs issued to techs.
    Boxs used in field.
    Boxs returned.

    The actual path of box is
    Added to warehouse.
    Issued to tech.
    Tech uses box in field or returnes it to warehouse.
    Boxs will be reissued to tech, unless the box is bad then it is removed from datebase.


    I'm just trying to find the best way to do this.
    I'm thinking of using a query to update the the tables according to where the boxs go.

    Not sure if I should have a master box list and have status on it set to warehouse or [tech #] and have other tables just update that one according to what happens.

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Hi Jay

    Hard to be certain based on the description however it sounds to me like you have a box entity and the box has an attribute (call it status) which can be:
    In Warehouse
    With Tech
    Bad

    Bad sounds like an invalid record in which case it should be deleted (???).
    Unless you need to track the status of the box (for example if it is in the warehouse do you need to know if it has only ever been in the warehouse, or do you need to differentiate whether or not it was in the warehouse then went to a tech and then went back to the warehouse) I would say a single table with a status field.

    Is there more to this than I have outlined above? Have a nose at the below. Does this help?
    http://r937.com/relational.html

    In particular, if a tech will make changes to the box then we need to look at your business requirements and see if what I suggest above is too simplistic. It is just a little too abstract so far to be certain....
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Nov 2003
    Location
    Sussex, England
    Posts
    404
    Is each individual box identifiable (serial no or similar)?

  6. #6
    Join Date
    Sep 2006
    Posts
    162
    All Serials Nos are unique. Will not duplicate it self.

Posting Permissions

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