>Hello Nadya.
>
>I believe your last statement needs a little bit of clarification. It should be reffered to this new added record, I believe. There are two articles in MSDN about similar bugs, but they both talk about insertion.
>
>I have an MSDN subscription and I have seen the articles. However, MSDN does not report all of VFP's little quirks and I have reported on some of them in sessions I have given at various conferences. Just because it is not documented in MSDN does not mean that it isn't so.
>

Right. I agree. I was looking at these articles, but could not find a resemblance with my situation until we found out, that the additional table, which was used for Lookup purposes in this grid, was a culpit.

>I was struggling with this bug for quite long time. Once I changed Buffering mode of the table, which was used just for Lookup purposes in the grid, to 5, the problem went away.
>
>I am sure that your knowledge and expertise regarding the use of grids in VFP is quite extensive and I appreciate the fact that you have been kind enough to share it with us. However, in my limited experience, using the REPLACE command to update the grid's RecordSource while the grid has focus causes Error 109.

Well, I see your irony :) The idea is that this message is sporadic (at least it was this way in my case) and again in one particular case setting buffering mode to 5 for both tables (main and Lookups) had resolved this issue for me.

May be I was just being lucky, or users don't report this problem anymore :)