If there isn't a record at all, I'm not sure what else you can do. Unless, in the SELECT statement, you try using the ISNULL() function around your tDBHReports columns.
Like:
Code:
SELECT tUnits.UnitNum, tUnits.UnitNameAbbrv, ISNULL(tDBHReports.QM231,'NADA'), ISNULL(tDBHReports.QM232,'NADA)......
FROM dbo.tUnits LEFT OUTER JOIN
dbo.tDBHReports ON dbo.tUnits.UnitNum = dbo.tDBHReports.UnitNum
WHERE (tDBHReports.RepPeriod = @Date) AND (tUnits.UnitNum = '36BG1')
Union all
Again, I'm not sure that will work or not. But in SSMS or QA, if you're running the code, then for every record in tUnits that is not in tDBHReports, then all the tDBHReports columns should return 'NADA' while the tUnits columns return proper values.
If there is a record in tDBHReports that isn't in tUnits, then this won't help you. If there aren't any records in either, then you won't get anything at all because you can't generate a record set on something that doesn't exist.
Anyway, you should be first testing your code in QA or SSMS before going back to the Matrix. Once you get your code there to display the records you want and display them correctly, then you can go back to SRS and attempt the Matrix again. But if your code isn't pulling what you want in QA/SSMS, then don't bother fiddling with Reporting Services because you're just going to get frustrated.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"