Exactly - in in VFP7 it was "Record in use by another..." and such message was completly missleading. New error message is much better but the problem still exist. Aleksey Tsingauz from Microsoft was helpfull in explaining reason of the error and the explanation shoul be in VFP help.

If I understand correctly - your company will make real windows not virtul.
In Poland this activity is quite big market - because windows made in old comunistic times was bad quality and there was and still there is many old windows to replace. It seem to me that replacing windows is better and easier bussines than making software :)


>Hi
>In my case, adding a new record was in KeyPress event of form. In VFP9, the error is the one you said, but in VFP7 is "Record in use by another...". Strange.
>And one can succed to corrupt the underlying table using this "technique" (duplicates with garbage in PK , even with primary key index)
>
>>Additional question: are you maybe going to conference in Prague (22-24 june) ?
>No, I cannot go. We are very busy , we are in process of opening a new company branch, we will produce Windows :-) ( no joke.)
>Only the software was 87K EUR - brrrr!
>
>Have a nice day.
>
>>Thanks Dorin !
>>It seems that my problem was in a way similar to your. But in my case moving focus from grid to page before actual action solve my problem. I found it just now. I needed just three additional lines of code in proper place - the three additional lines costed 12 hours of my time - quite nice result - isn't it :)
>>Additional question: are you maybe going to conference in Prague (22-24 june) ?
>>
>>
>>
>>>Hi Josef
>>>I've seen this error in one of my forms.
>>>Was related to Valid code for column textbox (some calculations and replaces). If I commented code from Valid method, the error dissapeared.
>>>Was reproductible, if one column textbox contain validation code with REPLACE ..., error always appeared when new record was appended via Keyboard (sometimes even changing current row with the mouse click)
>>>
>>>
>>>>I just waisted 8 hours fighting without results against undocumented vfp8 error 2072 (cursor contains unsaved changes...). The error is very hard to track. I tried the application also under VFP9 beta and unfortunatly I see the same bad behaviour. I can't create repro code. I searched UT messages and try some suggested solutions without happy end. It seems that the error is somehow connected to a grid placed on a pageframe page and the moment when new record is added and edited in buffered view. The troublesome form is very similar to other forms that work without any problem. In the moment I hate VFP ...uuuhhhhrrr...