>>>>>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?
>>>>
>>>>always expect the worst! i'd try the optimistic table buffering...
>>>if u say expect the worst - then it should be pessimistic buffering , no ? :)
>>>
>>>anyway, regarding the orig. q.
>>>as Dave and others said - use VFP's own buffering scheme
>>>preferably optimitic raw buffering (though in your case pessimistic raw buffering might be ok as well)
>>>using buffering is not to complicated and anyway if you write
>>>your code well u can use it (or most of it) in other apps.
>>
>>Arnon
>>
>>'optimitic raw buffering'? Don't you mean 'optimitic row buffering'? I waould hate to buffer anything Raw, especially steak!!!! (g)
>>
>>It's ALIVE! (g) Welcome back Kotter! (s)
>>
>>Tom
>
>waould, indeed!


I am glad I have so many buddies out there in La-La land.... (s)

Tom