Cyrus (sorry - I think I used your last name last time)

Using the info from MS in message #799473, I created a workaround in my situation. For me, the error was happening when focus was in a grid, and the user selected the "New" button, which added a record to the local view which populated the grid. This would qualify as changing the underlying data.

To resolve the issue, I intercept the new call and first set focus to another control, then add the record. The "feature" seems to be gone. It actually works out, because the users don't do data entry in the grid, so I just send them to the first control used for data entry.

The really weird thing is that I've had pretty much the same form working for about 18 months without previously hitting this error. I just recently upgraded the app to VFP 8, and the problem started.

Another interesting note is that the error is reported as an update conflict in VFP7. I had been getting wierd, un-reproducable update conflicts in the VFP7 version (using SP1, which fixed a bug in the VFP7 database container). Maybe VFP8 just made the bug reproducable, because it was happening very consistently.

Good luck!

David

>The description of the error is:
>
>"Cursor cannot be modified because it contains an unsaved record".
>
>I tried to look up the Error# and why it happens, but could not find it anywhere in the vfp8 Help file.
>
>So, I am wondering
>
>a) Why it is the error missing from vfp8 HELP file ?
>
>b) what does this error really mean ? and what is the best way to prevent it?
>
>Thanks a bunch...