>Hi.
>I'm writing a multi-user application and I have some questions about buffering:
>1. Is really necessary to use buffering?
>2. Which buffering method is "safer"? Record/Table (Pessimist/Optimistic)?
>Thanks in advance.
Apart from the less likely table corruption mentioned, quite simply, buffering allows you to provide the user with "Save" and "Cancel" buttons. In other words, you can have the TextBoxes, etc. on your form directly linked to the table fields (through the .ControlSource property), but only when the user presses a "Save" button will the changes be saved.
Also, any validation is postponed until the program tries to save the record.
In summary, I don't find Buffering absolutely necessary, but it is a great convenience.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
