entering resume info into microsoft access

[syid]

i'm trying to create a new database in order to keep track of basic info from
resumes: experience(just dates,title,and company-no descriptions), position
desired,contact info, etc. I have been using excel but now i want to see if
the Microsoft Access program is quicker and more efficient. Can someone help
me?

 

[Philip Herlihy]

i'm trying to create a new database in order to keep track of basic info from
resumes: experience(just dates,title,and company-no descriptions), position
desired,contact info, etc. I have been using excel but now i want to see if
the Microsoft Access program is quicker and more efficient. Can someone help
me?

Best thing I can suggest is:
Create a new blank database.
Go to the Tables section
Create a table by using Wizard - and pick a sample table that seems
appropriate.

The most important thing to get right is your table design. See:
http://tinyurl.com/ms-table-design-tutorial

HTH,

Phil, London

 

[Arvin Meyer MVP]

i'm trying to create a new database in order to keep track of basic info
from
resumes: experience(just dates,title,and company-no descriptions),
position
desired,contact info, etc. I have been using excel but now i want to see
if
the Microsoft Access program is quicker and more efficient. Can someone
help
me?

Quicker? Probably not until you have the database designed. Then yes.

More efficient? Without any question, yes.

So first, build a new, empty database, and import all the Excel data into a
new table. Wizards should do most of that for you. Now look at your data.
What's being repeated frequently? In a resume database, I'd imagine that at
the very least title, and position desired. Create new tables for these and
replace the descriptions in the main table, with the ID's from the new
tables. Now create forms for everything. Again in the beginning, you can let
the wizards do it for you, just replacing the ID field text boxes with combo
boxes, showing the title, but storing the ID. Do not fall into the trap of
using lookup fields, they are easier to design, but will cause immense
problems later:

http://www.mvps.org/access/lookupfields.htm