Recent content by mrr010

Thank you for your reply. Our staff work in shift 24/7, so I must record 7 days per week, but as you have pointed out, this size of data should be well within capabilities of Access. I will store about 2-3 years of daily attendance data for audit and analysis purposes. After that period, some of...

"Attendance (in hours)" is a day to day data. One staff, one day, one record. If the design of "Attendance_Records" is fine, then for 1,000 staff, the table will have 365,000 records per year. Therefore I will need a method to calculate a weekly sum (adding 7 records) for each staff, should I...

Hi, thanks for your reply. Yes, I dont want my Access structured like Excel that is exactly why I am building a new database. I am thinking of ways to populate my VBA generated data into the appropriate fields/tables while importing but I am not familiar with the ways/tools available.

I do not have access to log in and log out time. The attendance is manually written into the finance worksheet. The "Attendance (in hours)" should be directly imported from the VBA generated output. Thanks. For instance, this record from my VBA output: 10001 | XXX | Temp XXX | 7.50 (in...

Hi there, first of all I have no prior experience in building a database. The reason that I am thinking of building one is that excel files that my company is using are tedious, difficult to read and manage, and unable to meet our demands. My work: We closely keep track of a few hundreds to a...