Thanks, Jason!

Within 10 seconds I could see what the problem was and fixed it with a
few lines of code.

Basically, I had an open singleton select (I have a node editor
available for the tree) while sitting (after OnFocusChanged) on the tree
node. Because that is the corresponding record I was updating, when I
moved off the node that dataset was resetting what I had done behind its
back so to speak. To fix, I just posted any edits, closed then Updated,
then reopened the node's record in the tree node's query after looping
through the 1 or more Updates.

I remember a few years ago you were encouraging us to use this
component. I actually added it to my program, but kind of forgot about
it. This is the first time I used it for a "real" problem. I actually
have another tough problem for which it may be very helpful.

Chuck.

Jason Wharton wrote:

> My suggestion is to use the SQL trace monitor to carefully examine exactly
> what is being sent to the server. You may find some clues there.
>
> Jason
>
>