>>So MULTILOCKS will be set ON behind the scene when form is loaded? What and when (if any) will reset it back?
>
>It seems that it does not get set back. A private data session will protect the setting in the derfault data session though.

Jim, what do you think about other question derived from this thread: what's the necessity to have SET MULTILOCK ON in the case of row buffering, i.e. only one record seemingly would be locked? Is it just a precaution against some erratic user already locked (with RLOCK()) one record on the table and now started to edit another record with row buffering?