>Thanks Nadya. No not at all. It could be the EXACT same issue you are talking about.
>
>I have a form (the main form in a Order Entry application) with a grid that uses bunch of tables, and most of these tables are related and are openned in buffered mode 5. I also have a table or two that maye have the NOUPDATE (not NOMODIFY) keywork in their USE command. So, you could be right on the money!!
>
>So, what is your quickest and most straight forward way to check this theory out ?
>
>Are you saying maybe I should go ahead remove all NOUPDATE keyword from all tables used in that form (as well as all the tables used in CHILD forms that get loaded from this form) ?
>
>Cyrus
>

Hi Cyrus,

No, I'm saying, that even for these NOUPDATE tables you should set buffering mode 5. At least in my case where I displayed the related information from such NOUPDATE table in a grid adding buffering solved that problem.
>>Hi Cyrus,
>
>>Perhaps completely unrelated scenario, but we had similar problem ("Record in use") in VFP6. In my case the main table was in buffered mode 5. I have a grid on the form, which allows editting... There was another table involved in relationship (code and description). This table was used for display purpose only (e.g. code='5' meant "Unresolved", etc.) I used that table with NOMODIFY keyword. It turned out (after about a month of pulling hair out) that this table was a curprit. So, I opened it in buffered mode 5 as well and we didn't have that error since then.
>
>> Just wanted to let you know my experience and sorry, if it's a completely different issue.