MS Access Entry Amounts

A

ABC123

I am planning to create a database to monitor approx 500 employees
performance. I will hopefully be entering approximately 20 entries per month
for each employee in the database, and thus 140+/- per year in the table.
These entries will illustrate on what days the employees worked.

Is this possible or will this create far too many entries for MS Access? I
want to have the database for a good while (10yrs+) and so if I work it out
right, 140 (total entries per person per year) *500 (# of employees) *10 (#
of years) = 700000 entries in one table.

Would there be a better way to split up the tables and info?

To summise, there will be an employee, then their shifts worked per month
over 10 years.

I must highlight that the database will be on a network and thus split.

Many thanks :)
 
R

Rick B

Not sure why you would want to keep timecard data for more than a few years,
but Access can easily handle 700,000 records. Since it sounds like your
entry will be pretty simple and just a few numbers per record, I'm guessing
you could probably keep several decades of data before running into trouble.

I'm guessing you will have (at least) two tables. One for the employee
number, name, etc. and one for the detail records. I'd make sure to put an
"inactive" flag in my employee table and think about what you will do with
terminated employees and their data.
 
D

Dirk Goldgar

ABC123 said:
I am planning to create a database to monitor approx 500 employees
performance. I will hopefully be entering approximately 20 entries
per month for each employee in the database, and thus 140+/- per year
in the table. These entries will illustrate on what days the
employees worked.

Is this possible or will this create far too many entries for MS
Access? I want to have the database for a good while (10yrs+) and so
if I work it out right, 140 (total entries per person per year) *500
(# of employees) *10 (# of years) = 700000 entries in one table.

Would there be a better way to split up the tables and info?

To summise, there will be an employee, then their shifts worked per
month over 10 years.

I must highlight that the database will be on a network and thus
split.

Many thanks :)
Click to expand...

That shouldn't be any problem. Access has a file-size limitation -- 2GB
max; less than that practically -- not a record-count limitation, but I
wouldn't expect that many records to present any difficulties. And if
the file should start to grow too big, despite compaction, you could
split off old records into a separate MDB file and link that in, using
union queries to drive reports.
 
A

ABC123

Would there be a better way to split this down? Say per month or per
department or something?
 
D

Dirk Goldgar

ABC123 said:
Would there be a better way to split this down? Say per month or per
department or something?
Click to expand...

Splitting into separate files by month or by department sounds like a
bad idea. Probably your best bet, if you ever *have* to split your data
into multiple MDB files, is to put "inactive" data in a separate file.
By "inactive", I mean data that will not be updated, and (ideally) that
you don't often need to see. Since you'd need to use union queries to
bring *all* the data together, and union queries are not updatable, you
want to split out your data so that you don't often need to do it.
 
Top