My department has contracted a team to build a "bot" that will automatically assign work for employees in my department. It takes emails from an email inbox, looks at other Excel documents, and runs some queries to appropriately manage workloads and assign work evenly.
On the user end of things, we want to build an Access Database that will allow everyone in our department to track their workloads, be able to transfer work from one person to another, etc.
In the traditional way, I would start by making tables...but in this instance, all of the data is going to be dumped into Access from a single Excel table. Once the data is imported, how could I retrofit it to a relational database? For example, I would normally build a table for "Employees", I would have a PK of EmployeeID, I would have the First and Last names, maybe email address, etc.
The Excel document is only going to be showing the Employee's full name, what's the best way to tie this back to the Employee in the database?
On the user end of things, we want to build an Access Database that will allow everyone in our department to track their workloads, be able to transfer work from one person to another, etc.
In the traditional way, I would start by making tables...but in this instance, all of the data is going to be dumped into Access from a single Excel table. Once the data is imported, how could I retrofit it to a relational database? For example, I would normally build a table for "Employees", I would have a PK of EmployeeID, I would have the First and Last names, maybe email address, etc.
The Excel document is only going to be showing the Employee's full name, what's the best way to tie this back to the Employee in the database?