Confused @#%

[Anand Vaidya]

I have an attendance table tblDaily_Attendance where 1 record is added daily
for each employee.We have 175 employees in our company, so , for a month
(with approx. 22 working days ) , the no. of records goes to 175 * 22 = 3850
and for an year it goes to 175 * 22 * 12 = 46200.
From performance point of view, should I use the same table for the
attendance for the whole year or will it be better if I use one table ( like
tblDaily_Attendance_Jan,tblDaily_Attendance_Feb and so on) for each month?

 

[Duane Hookom]

One Table.

 

[Rick B]

In my opinion (and based on almost every entry previous post in this
newsgroup related to this) you should use one table period. Not just per
year, but forever.

This will allow you to compare one year to another, run historical reports,
etc.

There is rarely a need to "archive" data in an Access database or break data
into more than one table. With 50,000 records a year, you have absolutely
nothing to worry about for a very very long time.

 

[John Vinson]

I have an attendance table tblDaily_Attendance where 1 record is added daily
for each employee.We have 175 employees in our company, so , for a month
(with approx. 22 working days ) , the no. of records goes to 175 * 22 = 3850
and for an year it goes to 175 * 22 * 12 = 46200.
From performance point of view, should I use the same table for the
attendance for the whole year or will it be better if I use one table ( like
tblDaily_Attendance_Jan,tblDaily_Attendance_Feb and so on) for each month?

Certainly one table, with proper design and proper indexing (an index
on the date field and employeeID).

2,000,000 rows is a respectable sized Access table, 20,000,000 rows is
getting pretty big. You're NOPLACE close.

John W. Vinson[MVP]

 

[George Nicholson]

2,000,000 rows is a respectable sized Access table, 20,000,000 rows is

getting pretty big. You're NOPLACE close.

lol. gee John, trying to give the guy an inferiority complex or something?

--
George Nicholson

Remove 'Junk' from return address.