>I'm looking for suggestions/opinions regarding the easiest, least complex way (for both developer and users) to implement record locking for an intra-office app that will be simultaneously used by only 3 people sitting relatively close to each other. It's unlikely the user base will grow, and the users interact all day long and are aware of the overall workflow in the office.
>
>Because risk of an access conflict is so low, I've even considered NO record locking. (If one user has the paperwork in hand, it's unlikely that another will want or need to access the data related to that paperwork).
>
>Suggestions/Comments?

>> VFP buffering works extremely well, but for your case would be worthy to consider simple partition between View and Edit mode of application flow. I mean that all users can scroll tables to display information on read-only screens (no conflicts), but to edit a user will RLOCK() record on separate (very similar) screen, which can be even non-bufferde to avoid additional coding.