>>>OK, I've created a log and verified that my calculations are correct. But the text box does not show the correct value, although my log shows that it has the correct value!
>>>
>>>Here's an image of the screen and the log: http://www.samaansystems.com/images/Premium%20Problem%20at%20NEWIM.jpg
>>>
>>>What could be going on here?
>>
>>Well, strictly speaking. your log doesn't show that the Textbox.Text has the correct value - just that oPolicy.Entity.Premium has the correct value :-} How are the two bound ?
>>
>>Also, you mentioned earlier that this behaviour was occurring on a production server only but I see the browser is accessing localhost. Does this mean you are actually seeing the same behaviour in development ?
>>
>>Don't know if it's relevant but what, if any, is the relationship between 102.87, 1.35 and 104.22 ?
>
>The txtPremium.Text value is the correct 104.22 (from the log), but yet is displaying 102.87 on the form. I can't understand that.
>
>I didn't mention a production server, just that it's at a client. We are running it off the localhost at the client and no, I'm not seeing the same behaviour in development. On my system the textbox under the Premium label displays the 104.22.
>
>Yes, 104.22 = 102.87 + 1.35 and that is what my code does, sum those two values, then set the text value of txtPremium to the total value and set the entity's value as well. The txtPremium is bound to the entity's Premium value.

So, in essence, you are programatically setting the TextBox.Text value to 104.22 (.ToString()) and not relying on data binding as such?
Where in the page life cycle are you doing this?
Can you hook the Page.PreRender event and log the Textbox value there as it is going out the door? At least that might tell you whether the weirdness is occuring on the server or the browser.