Table/Field Name Question...

[WestSide2003]

Hi,

We are an Access Database.

We currently have a table called "Resumes" that we are storing information relevant to a "Resume" or jobseeker

There are many things that pertain to a resume that we want to include in our website

In creating our database tables, does it make sense to have 1 table called Resume and then just create all the fields within that one table??? (i.e, FirstName, LastName, DesiredSalary, WorkHistory, etc, etc)

Or have multiple tables like one table for "Contact Information", 1 table for "Work History", 1 table for "Cover Letters", etc, etc

I am a bit new to db design so any initial guidance would be appreciated.

Thanks,

WestSide

 

[Steve101]

Absolutely the latter (otherwise you may as well do it in a spreadsheet!). Find out about data normalisation and relational database design principals (any good Access intro book should have a section on this). Also check online help, or search for "database design" or "data normalisation" on the web.

In a nutshell, good database design is all about entering and holding data once, and not duplicating it; hense different tables are used to stored the different types of data, and relationships are then used to relate or join this data.

Good luck,

Steve Lewy
Solutions Developer
steve@lewycomputing.com.au
(dont cut corners or you'll go round in circles)

 

[JeremyNYC]

Steve is spot on, as is so often the case. Check out the Fundamentals article in the Developers' section of my website.

Jeremy ==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Affordable Development, Professionally Done

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.