All are saying the same thing...but I know I use the method Charlie
Coleman showed me probably 20 years ago using local cursors and having
my n-tier framework code handle the updates. I basically get the data
into a VFP cursor. For add/edit mode, I scatter the cursor into an
object and my edit forms use thisform.oRecord.Whatever for control
sources. If user wants to save, edit form sends back signal to calling
form which then passes the MyEditForm.oRecord object to the backend for
INSERT INTO or SEEK-and-GATHER for update operations. That's a
simplified process but that's basically it. But to be fair, I haven't
use DBFs in my designs since seeing Bob Lee's n-tier demo at WhilFest in
2002 or 2003. Prior to that, I used local VFP views (table-buffered)
for my apps.
On 11/25/2019 1:51 PM, Jürgen Wondzinski wrote:
Table buffering is very common. Basically all frameworks are using it.
Can't do any decent multiuser handling without it.
Yes you could do a simplier record-buffering mode, but as soon as you are faced
with the typical 1:n editform, then you would need to have tablebuffering
anyway.
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
