Sounds like a pretty typical many to many setup. Letters is the linking table with fks to both users and departments. So you just go in through the letters table, parameterizing on userid, and get letters.*, departments.* joining letters to departments.

Very much like a student registration app where you would say "Show me all the grades for Student X and the course info for each course where he has a grade "


>That's all I have. I got it from someone else. It's sort of vague.
>
>
>>It may help if you post create table statements and some input. Desired output will help as well.
>>
>>>Show 3 different ways to do the following:
>>>
>>>
>>>- Each department can have multiple users.
>>>- Each user can have multiple departments.
>>>- A letter belongs to a user and a department.
>>>
>>>Write a stored procedure that takes a UserID and returns all of the columns from
>>>the Department and Letter tables for each Letter for the UserID that was passed to
>>>the stored procedure.
>>>
>>>Here's one way that I came up with:
>>>
>>>

>>>
>>>CREATE PROCEDURE GetDeptLetters
>>>	@UserId		INT
>>>
>>>AS
>>>
>>>	SELECT d.*, l.*
>>>		FROM Departments d
>>>		JOIN Letters l ON l.DepartmentId = d.DepartmentId AND l.UserId = @UserId
>>>		WHERE d.DepartmentId = @UserId