That's an interesting issue, but it seems like the problem would be very application-specific. Implies that the underlying child table is being modified by other users and also by activities in the other (local) work area. Question is, in a buffered & shared environment, whose updates have the highest priority? In the case where you need to see buffered updates in the other local workarea that are not yet committed, then I think you have a good point.

>It will work but the purpose will not be achieved because you are pointing different table alias and might return wrong recno especially if the table is BUFFERED.