>>Yes, that would be expected behavior: if the datasession
>>changes, then the table that the grid is bound to is no
>>longer accessible, so it acts as if you've closed it.
>>Check out MSKB#Q260048 for details and a possible workaround.
>
>It seems that the problem occurs only if the form itself changes
>datasession rather than makes a call to another object to change
>the datasession. This seems like two different ways of doing the
>same thing where one way will work and another will fail. That
>sounds like a bug to me.

Well, the grid belongs to the form's datasession, so if you change the datasession of the form, it affects the grid. It will affect the other controls, too: it's just not as obvious as with the grid.

What do you mean by "makes a call to another object to change the datasession"? Can you provide code that shows what you mean here?