I have a table in my database called Employee. I also have a Job table that links one employee to each Job. My client wants to be able to add Employees (which should be easy), but also be able to remove Employees (when people quit, etc.). I don't want to just delete the employee from the table because that would possibly leave dangling pointers from the Job table (and I don't want to go through and re-assign the Jobs to different employees). I was thinking about adding another field to my Employee table that is called Active. If the employee is "removed", then active would be set to no. I have quite a few other tables where I would like to implement the same technique. Does anyone see a problem with this idea? Any better ideas on how to get around this? Thanks!