>>But then does form.activate() do that? Or do I need to set focus to something on it?
>>
>
>you can use ACTIVATE WINDOW or oform.Show
>but this doesn't activate oform's datasession
>because the READ EVENTS live in DATASESSIONID=0

This helped stop the grid refreshes.During this fight I've seen the datasession stay the same - 3 - even after me issuing a Set Datasession to this.nDatasession, which was 2. Now it works, and I really don't have the time to investigate deeper, there's a deadline on the horizon ;).

>what I can say is this:
>without using SET DATASESSION, an object cannot change it's datasessionid.
>FOR YOU ?

I've seen it continue to operate in the DS in which another object's code was executing, i.e. it wouldn't return to the caller's DS. With these form.activate()s, it started behaving properly - except the transaction level counting, which was also weird. But I've reshuffled the code so the transactions are now separated.