Hiya Jim ----

>
>That is only if you use Form Setting which I don't, I use BufferModeOveride on the cursors.
>
>It also doesn't address the situation with CursorSetProp(). I think the issue is burried deep in the VFP buffering implimentation adn that multilocks does something to allow multiple locks that also is neede for buffering to work. Pessimistic Table buffering is the ony one that would require multilocks. All of the others could be implemented with only one active lock at a time.

It looks like we're trying to delve into the minds of the Fox Team, eh? LOL...anyway, I don't use the Form setting either but I was thinking about this and believe that the Form setting introduces an ambiguity (row or table?) that may not be present all of the time, but may be present...therefore, it'd be a lot simpler for MS developers to just make an ON setting mandatory for buffering....can you imagine using the Form setting, adding a Grid, and getting an error message (MULTILOCKS ON Required)....PIA! So....IMHO that's a part of it.....

As to how buffering works: I agree 100% in theory but there has to be a reason for this. When you really think about it, SET MULTILOCKS is kinda BS as you would think that it'd be much simpler for VFP to not expose multi-locks and just assume ON when buffering was in use. I, for one, have never really concerned myself with how I wanted to set it...just thought "Hmmm...I'm buffering...better set it ON".....