Hi All-
I poked around existing threads for awhile and don't really see what I'm looking for. I appreciate any info that can be offered... and I apologize for my ignorance in database design and operation.
I have been reading Access 2010, The Missing Manual by Matthew McDonald to try and get a foundational understanding of how to approach database design. To that end, I have obtained plenty of understanding to get me going. The one point that troubles me, though, is the recurring sentiment that databases don't like repeated data. I'm trying to design a database to track semi-annual store inspections. By it's nature, this will mean some info will be repeated throughout the database (i.e. store number, region, inspection points, etc.). Granted, I'm planning on allowing the AutoNumber to designate each individual inspection as unique. I guess my question is this: does that provide sufficient uniqueness to overcome the fact that many, many of the fields will have recurring information?
I just wanted to proceed with care given that this is my first foray into database design.
Thank you in advance.