Hi,
We maintain employee records, mediclaim records, skill inventory records, and Birthday list separately in an Excel sheet. Instead of maintaining them separately in an Excel sheet, will MS Access help in maintaining them?
Regards,
Kavitha
From India, Madras
Acknowledge(0)
Amend(0)
2We maintain employee records, mediclaim records, skill inventory records, and Birthday list separately in an Excel sheet. Instead of maintaining them separately in an Excel sheet, will MS Access help in maintaining them?
Regards,
Kavitha
From India, Madras
Acknowledge(0)Amend(0)
Hello,
Microsoft Access can be very useful, but unfortunately, there is a learning curve. Access is a relational database that allows you to have multiple related tables. This is great for reducing redundancy but can be difficult if you have never done it before.
The basic concept is the elimination of duplicate data. For example, in a basic employee database, you could have an EMPLOYEE table. Each employee would have a single record or row in this table with a unique identifier. EMPLOYEE POSITION HISTORY could be a separate table. For each single employee record in the EMPLOYEE table, you could have multiple related rows in the EMPLOYEE POSITION HISTORY table based on each past position the employee has held.
Access can be a very powerful tool, but look into it before jumping in. I have seen many poorly designed Access databases in my time.
The link http://support.microsoft.com/kb/209534 provides some great information for DATABASE NORMALIZATION (Organization of Data) in Microsoft Access.
Good Luck!
Mark
Email: mark@hrdatamanager.com
From United States, Sonora
Acknowledge(0)Amend(0)
Microsoft Access can be very useful, but unfortunately, there is a learning curve. Access is a relational database that allows you to have multiple related tables. This is great for reducing redundancy but can be difficult if you have never done it before.
The basic concept is the elimination of duplicate data. For example, in a basic employee database, you could have an EMPLOYEE table. Each employee would have a single record or row in this table with a unique identifier. EMPLOYEE POSITION HISTORY could be a separate table. For each single employee record in the EMPLOYEE table, you could have multiple related rows in the EMPLOYEE POSITION HISTORY table based on each past position the employee has held.
Access can be a very powerful tool, but look into it before jumping in. I have seen many poorly designed Access databases in my time.
The link http://support.microsoft.com/kb/209534 provides some great information for DATABASE NORMALIZATION (Organization of Data) in Microsoft Access.
Good Luck!
Mark
Email: mark@hrdatamanager.com
From United States, Sonora
Acknowledge(0)Amend(0)CiteHR is an AI-augmented HR knowledge and collaboration platform, enabling HR professionals to solve real-world challenges, validate decisions, and stay ahead through collective intelligence and machine-enhanced guidance. Join Our Platform.
Emplyee Database Management.xls
Exit Management and Transition Checklist.pdf