The DELETE statement

I suspect that you have referential integrity enabled on EmployeeID to ensure that a store doesn't refer to a non-existent employee -- and then you are likely trying to delete an employee.

0) Deleting is not generally a good idea, try setting a status instead.
1) Or, remove the reference in Stores before deleting the employee.
2) This may be done by enabling cascaded deletes, but that is not a very good idea.


The reason not to delete records (such as employee records) is so you have a history of what happened in the enterprise. With a record of start and end dates you can easily query things like "when did Bob work for us and in what store?" -- if you delete the Bob record you have no way to achieve that. You will find that this is how business software works. Even if this is a student project, please do it this way to get in the habit -- it should lead to a better grade as well.

Since the data is being referenced and acts as a foreign key for another table, you need to change the value for the dependent table and then try to delete the record

You will trying to delete the referred record of the table. before deleting this record update the reference table value with different value or update those values as null and then delete the following row in the parent table.