>Hi.
>I'm writing a multi-user application and I have some questions about buffering:
>1. Is really necessary to use buffering?

You can write an application w/o it so obviously it's not necessary. However, with a buffering you only modify underlying tables when you submit changes (TABLEUPDATE()). It makes VFP table/index corruption less possible.

>2. Which buffering method is "safer"? Record/Table (Pessimist/Optimistic)?

It depends on definition of "safer". :)
The best is optimistic table buffering. It'll work with local VFP data and with remote client-server databases. And you've full control when data is updated.
The row buffering is dangerous because the data can be updated w/o your knowledge when a record pointer is moved in a view/CA cursor.
The Pessimist buffering can create contention issues and is not supported for client-server databases.