>>>I've just been trying something to see if the problem was related to the binding. I added in another textbox on the form which was not bound to anything and set that textbox's text value during the calculation, but it does not get set up when the calculation is called from the grid's update code. It does however get set when the calculation is called from outside of the grid. The grid is in an asp updatepanel, could this have something to do with it?
>>>
>>>If I remember correctly the updatepanel is supposed to be AJAX magic, is that right? Is there something that needs to be configured on their server to make AJAX work? Or am I going down the wrong path here?
>>
>>
>>You need a scriptmanager control on the ASPX page (it can be on the masterpage if there is one).
>>
>
>Yup, got one.
>
>>If you have controls in an updatepanel and changes to them will affect controls outside the updatepanel, the affected controls will NOT get updated to the client until a full postback occurs (when controls in an updatepanel are updated, that is called a PARTIAL postback).
>>
>
>This is what appears to be happening at the client site, but why should it function differently at my site?

I do not know why it would be different on a different site. I've never run into that issue. I'm assuming they are running the site in IIS (not mono or something) and they have the correct .NET runtimes installed?

You might want to include the correct AJAXCONTROLTOOLKIT.DLL (the exact version specified in you web.config) in the Bin folder of your site. This ensures the website uses that particular version.

>
>>You can set controls in an updatepanel as triggers that will cause a full page postback when they change, or you can add any controls that will be affected by updatepanel controls to the updatepanel.
>>
>>As a test, you might put your updatepanel (and contenttemplate tags) around all the controls on the page instead of just a subset and see if everything updates correctly. If so, you have a good idea of the culprit.
>
>I'll try that.