Just an observation, warning, and question... When you delete an employee entry, their names will be removed from all workorders and replaced with the next alphabetical employee from the employee list. We ended up having a supervisor credited with a lot of the work from a former employee...

Now, we use the "shift" value as a filter to determine who our current employees are.

Is there a better way around this?

Cheers,
Jack

The history should be maintained. If you delete an employee, their record in the work order history should be left unchanged.

If the employee is on any open work orders or assigned to any tasks it will not allow you to delete the employee through MP2, you would have to delete in manually in the database which is not recommended.

The filter method on Shifts is probably your best bet. I recommend adding a ZZ- in front of any former employee's name then creating a filter to remove anything beginning with ZZ-. I like this method because it lets everyone quickly identify that the employee is no longer with the company when they see their name listed on a work order.

What version of MP2 are you using?

Jonathan,
Thanks for the reply. We are using the "access" version. We haven't updated, because I felt that the newer version had less features...

I'm pretty sure we lost some of our history. One of the other problems we had, was when an employee is deleted, if they are assigned to any Tasks, the next alphabetical person will be inserted.

I have compared the two verison extensively, I don't believe there is anything in the Access version that is not in the 6.0 or 6.1 version of MP2. There are some new features in the new versions though. But I always recommend if it is working well for you, I wouldn't switch. The old saying if it ain't broke don't fix it.

Yes, I have ran accross that issue in the Tasks, the best way would be to go into the tasks table and search for all the Tasks assigned to the user you are deleting then reassign them before deleting the employee. If you delete the employee at all, I don't think it is always the best situation for all cases.

The reason Employees table and the Users table are seperate is for this reason. You can delete a user when they are fired since nothing is assigned or uses the User ID besides access to the software. Employees from the employee table were not intended to ever be deleted.

Here is an alternative to deleting employees that I often suggest-
In the labor table, rename the class field (via security) to current employee and enter Y or N for each person.
On the work order, labor tab, set up and save a filter with the condition "current employee is equal to Y." This will pull up the current list of employees and you won't need to worry about compromising your work history.
I hope this helps

Regards,
Jennifer