Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Moving Records to Fields

Discussion in 'Information Technology' started by BradMFischer@gmail.com, Jul 28, 2006.

  1. BradMFischer@gmail.com

    BradMFischer@gmail.com
    Expand Collapse
    Guest

    Is it possible to make the records of one table the fields of another
    table?

    Here's my scenario... I'm building a DB to keep track of software owned
    vs installed for a school. As I have the DB designed currently, one
    table is called tblSoftwareOwned. Here are some of its fields and a
    sample record.

    FieldName Record 1 Record 2
    SoftwareID MSOffice03 TypetoLearn
    SuiteTitle Microsoft Office 2003 Type to Learn
    Manufacturer Microsoft Sunburst
    Platform Windows Windows

    The purpose of this table is to keep track of info on each software
    title.

    I started creating another table called tblSoftwareInstalled, as
    illustrated below:

    Field Name Record 1 Record 2
    ComputerName Rm214-1 Rm214-2
    MSOffice03 yes yes
    TypetoLearn no yes

    The purpose of this table is to keep track of what is installed on each
    computer.

    So, as I add new software titles, with my current design, I will need
    to add a record to tblSoftwareOwned and then also add it as a field in
    tblSoftwareInstalled. Is there a way to make it dynamically become a
    field in the second table after I add it as a record in the first one?
    Or, is there another design that I should be considering?

    (For what its worth, there are tables in this DB design, such as
    tblvendor and tblorders - which, for example, keep track of who the
    software is ordered from and when the software was ordered.)

    Any feedback would be greatly appreciated.
     
  2. Loading...

    Similar Threads Forum Date
    Islam Moving Mountains Interfaith Dialogues Nov 29, 2012
    World Man punches nurse for removing wife's burqa Breaking News Dec 25, 2011
    SALDEF Stop Arizona From Removing Balbir Singh Sodhi from 9/11 Memorial Sikh Organisations Apr 27, 2011
    Moving Forward, Or Sliding Backward Sikh Sikhi Sikhism Oct 20, 2010
    Moving to Montreal, Canada Need Help! Community Out-Reach Oct 18, 2010

  3. Bill Edwards

    Bill Edwards
    Expand Collapse
    Guest

    Your table design is not normalized.

    tblComputer
    ComputerId
    Location

    tblSoftwareOwned
    SoftwareID
    SuiteTitle
    Manufacturer
    Platform

    tblSoftwareInstalled
    ComputerId
    SoftwareID


    <BradMFischer@gmail.com> wrote in message
    news:1151466214.353018.279940@m73g2000cwd.googlegroups.com...
    > Is it possible to make the records of one table the fields of another
    > table?
    >
    > Here's my scenario... I'm building a DB to keep track of software owned
    > vs installed for a school. As I have the DB designed currently, one
    > table is called tblSoftwareOwned. Here are some of its fields and a
    > sample record.
    >
    > FieldName Record 1 Record 2
    > SoftwareID MSOffice03 TypetoLearn
    > SuiteTitle Microsoft Office 2003 Type to Learn
    > Manufacturer Microsoft Sunburst
    > Platform Windows Windows
    >
    > The purpose of this table is to keep track of info on each software
    > title.
    >
    > I started creating another table called tblSoftwareInstalled, as
    > illustrated below:
    >
    > Field Name Record 1 Record 2
    > ComputerName Rm214-1 Rm214-2
    > MSOffice03 yes yes
    > TypetoLearn no yes
    >
    > The purpose of this table is to keep track of what is installed on each
    > computer.
    >
    > So, as I add new software titles, with my current design, I will need
    > to add a record to tblSoftwareOwned and then also add it as a field in
    > tblSoftwareInstalled. Is there a way to make it dynamically become a
    > field in the second table after I add it as a record in the first one?
    > Or, is there another design that I should be considering?
    >
    > (For what its worth, there are tables in this DB design, such as
    > tblvendor and tblorders - which, for example, keep track of who the
    > software is ordered from and when the software was ordered.)
    >
    > Any feedback would be greatly appreciated.
    >
     
  4. Brad

    Brad
    Expand Collapse
    Guest

    Thanks for the insight... I see what you mean. I'll see if I can run
    with this tip. I appreciate the help.
     

Share This Page