Huge Spreadsheet

I have inherited a HUGE spreadsheet that consists of 15 columns, and over
5000 records.

It is a list of employee reviews.

The Column Headings a Employee name, Review date, Rating, comments, etc.
So one employee would have several "records" or rows, one for each review.
I would like to pull over records based on certain criteria, such as employee
name, date, etc.

Is this an application for ACCESS?

Thanks!!

--
Jeff

"Jeff" schrieb im Newsbeitrag
...
I have inherited a HUGE spreadsheet that consists of 15 columns, and over
5000 records.

It is a list of employee reviews.

The Column Headings a Employee name, Review date, Rating, comments,
etc.
So one employee would have several "records" or rows, one for each review.
I would like to pull over records based on certain criteria, such as
employee
name, date, etc.

Is this an application for ACCESS?

Thanks!!

--
Jeff

Access could handle this quite effectively.
--
Duane Hookom
Microsoft Access MVP


"Jeff" wrote:

I have inherited a HUGE spreadsheet that consists of 15 columns, and over
5000 records.

It is a list of employee reviews.

The Column Headings a Employee name, Review date, Rating, comments, etc.
So one employee would have several "records" or rows, one for each review.
I would like to pull over records based on certain criteria, such as employee
name, date, etc.

Is this an application for ACCESS?

Thanks!!

--
Jeff

"Jeff" wrote in message
...
I have inherited a HUGE spreadsheet that consists of 15 columns, and over
5000 records.

It is a list of employee reviews.

The Column Headings a Employee name, Review date, Rating, comments,
etc.
So one employee would have several "records" or rows, one for each review.
I would like to pull over records based on certain criteria, such as
employee
name, date, etc.

Is this an application for ACCESS?

Thanks!!

--
Jeff

To add a bit to previous answers, a simple design could be sufficient, given
what you've provided.
Consider an Employee table, with columns for data related to the employee
(including a unique identifier, or primary key, for each employee, such as
an employee number). A second table, Ratings, would have columns for data
for each rating and include a foreign key column to associate each rating
with an employee.

To add a little more, I would consider further normalizing your "spreadsheet"
so that each rating doesn't have its own column. There is a sample employee
evaluation MDB available at:
http://www.rogersaccesslibrary.com/f...8e8 ze79a949f
--
Duane Hookom
Microsoft Access MVP


"PvdG42" wrote:


"Jeff" wrote in message
...
I have inherited a HUGE spreadsheet that consists of 15 columns, and over
5000 records.

It is a list of employee reviews.

The Column Headings a Employee name, Review date, Rating, comments,
etc.
So one employee would have several "records" or rows, one for each review.
I would like to pull over records based on certain criteria, such as
employee
name, date, etc.

Is this an application for ACCESS?

Thanks!!

--
Jeff

To add a bit to previous answers, a simple design could be sufficient, given
what you've provided.
Consider an Employee table, with columns for data related to the employee
(including a unique identifier, or primary key, for each employee, such as
an employee number). A second table, Ratings, would have columns for data
for each rating and include a foreign key column to associate each rating
with an employee.