RE: Tables Question

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Ron Erwin (ronerwin_at_u.washington.edu)
Date: 10/03/04

  • Next message: John Vinson: "Re: Combo Box" 
    Date: Sun, 3 Oct 2004 16:33:30 -0700
To: Karen <Karen@discussions.microsoft.com>

    You need to design your tables and database...

    First put similar fields together.. then identify keys for these tables..

    Determine the relationship between the tables and add foreign keys as
    needed to handle one to many relaionships .. or many-to-many
    relationships.

    I can see several tables:

    Salesman Personal info

    Earnings
      Earnings type (key) Real/Projected

      You can carry the type values in a third table.

      Follow the database normalization processes.

    Ron Erwin
    (206) 465-8484

    ====================================================================

    Business Administration (Information Systems)
    Music Minor (Voice, Keyboard)

    ====================================================================

    On Thu, 30 Sep 2004, [Utf-8] Karen wrote:

    > They may have CommittedBus for 2004 and 2005. Not sure how to separate the
    > years.
    >
    > "anonymous@discussions.microsoft.com" wrote:
    >
    >> Just an idea, but what about:
    >> tblPlans
    >> Year
    >> Salesperson
    >> SalesPlan
    >> CommittedBus (filled in as the year progresses)
    >> ProjectedBus (filled in as the year progresses)
    >>
    >> These records could later be sorted and filtered on the
    >> year field if desired.
    >>
    >>> -----Original Message-----
    >>> I have currently have multiple tables with the following:
    >>>
    >>> tbl2003Plans
    >>> Salesperson
    >>> 2003SalesPlan
    >>> CommittedBus (filled in as the year progresses)
    >>> ProjectedBus (filled in as the year progresses)
    >>> tbl2004Plans
    >>> Salesperson
    >>> 2004SalesPlan
    >>> CommittedBus (filled in as the year progresses)
    >>> ProjectedBus (filled in as the year progresses)
    >>>
    >>> I know this is not good table design. I do not know how
    >> to best design the
    >>> tables so that I do not have to create a table for each
    >> new year of business.
    >>> I have a salesperson table with the names of the sales
    >> people.
    >>>
    >>> Thanks for any advice.
    >>> .
    >>>
    >>
    >

  • Next message: John Vinson: "Re: Combo Box"

    Relevant Pages

    • Re: design question
      ... Are you sure you don't mean "primary keys made up by composing several ... The second stage was logical database design, ... SQL modeling and relational modeling that I've since seen in this newsgroup. ...
      (comp.databases.theory)
    • Re: [OT] Normalization
      ... >> primary keys on every database table. ... >> changed the database design for those situations was to provide a better ...
      (comp.lang.php)
    • Re: Relation Schemata vs. Relation Variables
      ... Identity beyond that provided by the identifying keys is a nonsense. ... design a system whether a key that appears to be very stable will remain ... I was called in to fix a problem at a company where management ... During that period the database became corrupt because it allowed changes ...
      (comp.databases.theory)
    • Re: Relation Schemata vs. Relation Variables
      ... Identity beyond that provided by the identifying keys is a nonsense. ... design a system whether a key that appears to be very stable will remain ... I was called in to fix a problem at a company where management ... During that period the database became corrupt because it allowed changes ...
      (comp.databases.theory)
    • Re: Key attributes with list values was Re: What are the differences ...KEY
      ... Jane Harper is married. ... And a constraint that states that single people cannot become divorced. ... database, or users, for that matter, to distinguish between them. ... That's the whole point of keys. ...
      (comp.databases.theory)