I have an issue again regarding output..

SELECT 'Jablonski, Karla',0,5,18,23 UNION ALL

SELECT '    Philip',1,5,7,12 UNION ALL

SELECT '        Rance, Martine',2,5,2,7 UNION ALL

SELECT '            Nagy, Helvetius',3,2,0,2 UNION ALL

SELECT '                Sommer, Martin',4,0,0,0 UNION ALL

SELECT '    McKenna, Patricia',1,6,0,6 UNION ALL

should be  :

SELECT 'Jablonski, Karla',0,5,18,23 UNION ALL

SELECT '    McKenna, Patricia',1,6,0,6 UNION ALL

SELECT '    Philip',1,5,7,12 UNION ALL

SELECT '        Rance, Martine',2,5,2,7 UNION ALL

SELECT '            Nagy, Helvetius',3,2,0,2 UNION ALL

SELECT '                Sommer, Martin',4,0,0,0 UNION ALL

Going that the M comes before P - even though Phillip as no LastName the combined result of LastName, Firstname means  that McKenna must come first.

karinloos,

The rule 5 says:

"The employees should be ordered by lastname, firstname"

In my opinion it does not refer to the combined result but "order by lastname, firstname".

I have many issues regarding the logic testing, in spit of I could fix my solution to avoid them, I should mention that they contradact with what have been said in the challenge forum, So I expect that you fix the logic testing sandbox to meet the asumptions you announce in the challenge forum.

Issues as I see them are:

1- from the logic tesing comments "An employee's first name is null, another one has null last name." but from the challenge forum "Columns EmployeeID , FirstName and LastName are all "NOT NULL".  ".

2- " An employee reports to a non-existent employeeid. Should be ignored. A couple of employees are self-reporting: same reportsto as employeeid. Should be ignored too." from the challenge forum " There is a foreign key constraint from ReportsTo to EmployeeId".

Finally I have a comment regrading one point in the logic testing "OrderID repeated for the same employee. Should count only once." because I could not find in the challenge anything enforcing that, and I do not see this as logic to be tested,because you accept same order id to be used for other employees. so either you enforce uniqueness or accept dulicates, and this my viewpoint and it is not necessary correct.

I am waiting your reply to know what I need to fix in my solution.

I found the same as Pasha on his Item 1.  The forum did specify that employee's first and last names could not be null.

The duplicate order id for the same employee was not addressed.  I too would like to know if  I need to fix that.

Thanks.

Yes it looks good to me now.