>You lost me on the data bound/unbound interface. I'm a novice and need a little more specics. Or at least where to find more specic info. Thanks.
>
>As to buffering, my form has pessimistic buffering set. I have multilocks set to on. I have exclusive set to off in the init method of my form.
>
>Thanks for your help.
>
>--lincoln

Data bound interface means that all controls directly linked to appropriate data fields, i.e. Textbox1.Controlsource='tabel1.field1', etc. This approach will require to use some kind of buffering. Pesssimistic buffering assumes that VFP itself will lock a record when user starts to edit, it's very similar to plain no-buffering situation and can lead to 'frozen' situation if you don't supply cushions (e.g. start editing session explicitly clicking 'Edit' button). Honestly, I never use pessimistic buffering, and cannot say more here. Optimistic buffering is much more popular way because here you allow users to edit the same record (absolutely no frozen forms) but it's your responsibility to handle multi-user collisions when user saves a record. Probably, optimistic row buffering will be good for you. Personally, I prefer to use unbound interface (no controlsources) which works like elastic combination of pessimistic/optimistic buffering.
All this is just short description. You could get much more information from Developer's Guide. However, if you have any questions about details, that's OK.