>Hi Nadya
>
>Are you using private data sessions?
>

Yes, of course, though in my test form example I forgot to set it to private. It don't make a difference, though...

>>>Hi!
>>>
>>>Yes, it would be good if you create a simple sample and manage to reproduce the problem using it at your side. If this is a critical bug/problem in VFP, you will have ready sample to post as bug-reporting to MS.
>>
>>I've created a simple form to reproduce this. I can send it to you, but you should be able to easily reproduce this problem by yourself.
>>
>>Create a form. Drop a table in its DE, set buffering mode to 5. Drop another table, set it read-only, no buffering.
>>
>>Put grid on the form based on the first table and add one field from the other table (this column would be read-only). Open two instances of this form and try to edit different fields in the same record. You would get Record is in use error. Now change the buffering mode of the second table to 5 and the error goes away.
>>
>>
>>
>>>>>Hi!
>>>>>
>>>>>If you have a simpe sample source code, can you send it to me?
>>>>
>>>>I didn't yet created a test to reproduce, but the steps I described would be efficient. I can create a test case at work and send to you.
>>>>
>>>>>
>>>>>>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.