Thanks for your reply, but your article really only addresses a very small part of the problem.

The requirement is to be able to check Active Directory to find out what...

It would seem that SSRS is the poor stepchild in the Microsoft SQL Server hierarchy! The "warning" I was receiving, even after coding a .NET 2 Framework process to...

True, but I should have given more details about the application this was designed for. It is a project management application, in which a project manager selects a project...

I've reworked the script to create History table rows only for columns that have actually changed in value. Here is the revised version:

/****** Object: Trigger [dbo].[upd_trg_SCD_Project] ...

Actually, to continue my response, you are correct in saying that an app, if it does a "blanket" UPDATE to all columns, will create history table rows, regardless of whether...

Yes, that would be correct. In this case, the requirements were to show a Field History, and if someone is changing the value in a column, and then perhaps...

. . . and, then, in SSRS:

=code.NLString(Fields!ProjectDuration.Value) + " Months"

So, basically, we are "fooling" SSRS into not worrying about whether that column's value is Null!

See last paragraph of my original posting - here's the function I actually used (although my original complaint still holds, that SSRS should not have made this necessary!):

PUBLIC FUNCTION NLString(ColData)...

Yes, in fact, that was the first attempt - same result - #Error.

Again, I strongly suspect that SSRS grabs a row of data, scans the report definitions, and decided that...