Terry,
Thanks for the tip.
Finally got the problem solved.
Apparently indexing with a tag "deleted()" was the source of the problem.
Switching the tag to "not deleted()" resolved it. How, I don't really understand.
Here's what we found.
With the tag deleted(), when the first client adds a record (and the second ent working on the same screen but different record), the record never gets updated to the second client's data environment when the first appends records. In the browse window (of the second client), we noticed that the record added is there when set dele is off but immediately disappears when set delete is on hence the second client never gets to see the record until it exits the screen and go in again.
With the tag set to "not deleted()", the record then almost immediately appears in the second client after doing a "locate" and "go bottom" to refresh the table buffer.
The same thing happened when using one PC with 2 sessions of the same screen.
So if there's a logical explanation for the above, do let me know as I'm still baffled by it and am just glad that it is resolved.
Yau