Results 1 to 5 of 5

Thread: database design

  1. #1
    Join Date
    Feb 2009

    Exclamation Unanswered: database design

    Hello guys,
    I'm using database access and I'm having a question in the design.
    which is better?
    having a table that you know would have duplicate records, i.e. 2 records of each user
    or having two tables with normalized relationship of one to one.

    waiting for your reply.


  2. #2
    Join Date
    Feb 2004
    In front of the computer
    Provided Answers: 54
    Without knowing what you are storing and more importantly what criteria matters for picking which design is "better" I have to make a guess. In most cases, it is better to have one table than to have two tables.

    I'm moving your thread to the DBForums Microsoft Access Forum. It will probably get better answers there than in the Database Server Software | Other Forum.


  3. #3
    Join Date
    Jun 2005
    Richmond, Virginia USA
    Provided Answers: 19
    Neither, if by "duplicate record" you actually mean duplicate record; two records in which every single piece of data is identical. What would be the point? Both designs would violate the principles of normalization.

    Why do you feel the need to have two identical records?
    Last edited by Missinglinq; 03-25-09 at 07:21.
    Hope this helps!

    The problem with making anything that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  4. #4
    Join Date
    Nov 2007
    Adelaide, South Australia
    ▲ What he said
    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

  5. #5
    Join Date
    Dec 2007
    London, UK
    Neither. No table should contain duplicate rows and if you design according to good principles then it should not be possible for the same row to appear in two different tables either. In fact you can go further and say that it shouldn't be possible for any tuple that is even part of some row (including both key and non-key attributes) to appear in more than one table.

Posting Permissions

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