That's not a bad idea, but it seems unlikely - a null value
somewhere would show up, I think, each time the user tried to log
in. Little, if anything, can change in the relevant data between
log ins.
I don't know which "line 5" it could be. The code for logging
in calls a template, a custom tag and initializes several cfc's.
In my experience, "line 5" could be referring to anything
that's called. Unfortunately, I only know how to narrow down the
offending file by having debugging turned on, which means I have to
have a reproducible error. The debugging output indicates what
template, tag or cfc threw the error. I haven't been able to find
any way of getting this info from an exception without it. None of
the "error' variables seem to give what I want.
I've designed a large and complex site. The odds are that
it's something in my code. Nevertheless, I'm very suspicious in
this case that it isn't.