>I recommend optimistic buffering:
>
>

>CursorSetProp("Buffering", 3) && optimistic row buffering
>
>or:
>
>CursorSetProp("Buffering", 5) && optimistic table buffering
>

>You no longer need explicit table locking. TableUpdate() will implicictly lock the record, for the short time the record is saved. It will also detect whether another user made changes in the meantime. TableUpdate() will fail in this case (with the default options - see the help file). The user will have to undo in this case.

>Since this is a rare case, and it is an advantage to have records locked only for a very short time (and only if the user really decides to save!), optimistic buffering is usually recommended.

Yes I've been using optimistic record locking in my applications, just was wondering how it works with views and if I'd need to make any changes on my programs.

>>Please don't think my questions are stupid or something, I know I can read about views on the VFP help and many of my doubts will be answered but I always prefer having real world answers.
>
>Feel free to ask. In general, no question is considered stupid on this forum - whether it be a beginners question, or an advanced one.
>
>And the VFP is not always quite clear on some details.
>
>Saludos, Hilmar.
>
>Oh, BTW, we can switch to Spanish whenever you like - although I see that you don't have problems with English.

Thanks Hilmar you've been very helpful, as usual. I prefer the english forum because most of the members post here but I'll be contributing on the spanish's too.

Enmanuel