Not at all:) You tried to counteract against a well known behavior of foxpro. It has nothing to do with relation, try removing the relation and use whatever 'current' record of nonbuffered table is.
Cetin

>Morale of the story - don't use SET RELATION in the application :)
>
>>Hi everybody,
>>
>>Ok, my colleague and I were able to identify the source of the problem.
>>
>>To make the story short, I skip all our trials and here is the reproducable scenario: (VFP6.0 SP4):
>>
>>Put a table in buffered mode (5) on a form. Open another table non-buffered shared noupdate. Make a relation from first main table into this one. Put a grid on the form. Put one field from related table into this grid (other fields from the "main" table). Run two instances of the form (we did this on two different machines). Both tables are on the network, as well as the form. Choose the same record in both forms instances. Change field on one grid (don't move from this field) and try to change another field on another instance (same record). You would not be able to do so (record would be locked).
>>
>>So, here is completely reproducable scenario. Let's call this "ISSUE" according to new George's terminology.
>>
>>Well, I guess it's the same problem, I was referred by Elmer Adkins too, but I didn't think it was it, since I don't do any insertions.
>>
>>So, I would really appreciate, if somebody would be able to reproduce this problem. I also would be interested to know, if this problem is resolved in VFP7 or not.
>>
>>Thanks a lot in advance for trying.