>
>I'm in the midst of rebuilding my workstation so I don't have VFP9 installed yet to test. But here's one theory:
>
>- A spinner is designed to be clicked on many times. In fact, IIRC if you click and hold an up or down arrow on a spinner it "accelerates".
>
>- If you bind a column to the spinner, and it works as you seem to expect (i.e. updating the underlying column on each .InteractiveChange), then you could be forcing tens of updates per second during accelerated spinning. Also, any code you have in .InteractiveChange will also be called tens of times per second. This could cause a lot of network/DB traffic. Also, if you're using a framework that tracks whether a field's value has changed as a result of user input, any such code will also be heavily exercised.
>
>- Instead, what you *probably* want is to hook code into the MouseUp event of the up or down arrow (or of the whole spinner itself, if either of these events exist) so as soon as you release the mouse button, the related fields get updated once, not during all the intermediate values you don't care about.
>

I think this is an excellent suggestion. And your explanation of why the value of the bound field does not change in InteractiveChange of spinner makes sense.

Thank you very much for your help and suggestions.