I read the contents of one particular column of the inserted table, but it is mysteriously not there. I get zero (datatype is money, Null). Immediately after the trigger fires, I SELECT from the table and the column has been inserted correctly. I'm doing similar things with other columns, and all is well there.
I've tried adding some logging into a log table to verify my observations (INSERT INTO LogTable SELECT MissingCol, GetDate() FROM inserted). I've done extensive work with triggers for years, and I'm pretty sure I'm doing all the normal things correctly.
There's really no other code to show. I'm thinking this is a SQL bug of some sort but I haven't found it yet on the MS site. Has anyone encountered such an anomaly?