Re: value is null or not an object, but its defined?
"cwizard" <cwizard@giblet s.com> wrote in
news:HxnIb.4531 $zx2.2090@newss vr23.news.prodi gy.com:
[color=blue]
> "to heave chunks" <justyaz@aol.co mpels.me> wrote in message
> news:2003123018 0241.16180.0000 1361@mb-m22.aol.com...
>[color=green]
>> var base = document.frmKit Amt.txtTotalKit Value.value;
>> var margin = document.frmKit Amount.margin.v alue/100;
>>
>> If you notice, you have a different form name for margin. It
>> should read
>>
>> var margin = document.frmKit Amt.margin.valu e/100;[/color]
>
> I'm so stupid.
>
> THIS is exactly why I came to you guys!!!!
>
> HAHAHAHAHAHAHAH ! THANKS![/color]
That sort of error is extremely common because of the phenomenon known as
"psychologi cal set" which is the built-in human tendency to adjust our
perceptions to match our expectations (Douglas Adams made it the basis for
his SEP field). Everyone who's ever debugged a program or proofread a
manuscript has spent long hours staring at his creation and seeing what he
meant to write rather than what he actually wrote.
Often a fresh pair of eyes is exactly what's needed to catch this sort of
problem, but do keep in mind the advice another poster gave you earlier in
this thread; try stripping down your code to produce a bare-minimum test
case. More often than you'd think, the mere process of doing that disrupts
the "SEP" mechanism enough to make your mistake visible to you.
"cwizard" <cwizard@giblet s.com> wrote in
news:HxnIb.4531 $zx2.2090@newss vr23.news.prodi gy.com:
[color=blue]
> "to heave chunks" <justyaz@aol.co mpels.me> wrote in message
> news:2003123018 0241.16180.0000 1361@mb-m22.aol.com...
>[color=green]
>> var base = document.frmKit Amt.txtTotalKit Value.value;
>> var margin = document.frmKit Amount.margin.v alue/100;
>>
>> If you notice, you have a different form name for margin. It
>> should read
>>
>> var margin = document.frmKit Amt.margin.valu e/100;[/color]
>
> I'm so stupid.
>
> THIS is exactly why I came to you guys!!!!
>
> HAHAHAHAHAHAHAH ! THANKS![/color]
That sort of error is extremely common because of the phenomenon known as
"psychologi cal set" which is the built-in human tendency to adjust our
perceptions to match our expectations (Douglas Adams made it the basis for
his SEP field). Everyone who's ever debugged a program or proofread a
manuscript has spent long hours staring at his creation and seeing what he
meant to write rather than what he actually wrote.
Often a fresh pair of eyes is exactly what's needed to catch this sort of
problem, but do keep in mind the advice another poster gave you earlier in
this thread; try stripping down your code to produce a bare-minimum test
case. More often than you'd think, the mere process of doing that disrupts
the "SEP" mechanism enough to make your mistake visible to you.
Comment