I use either of 2 solutions.

For a couple or so editable fields I keep those field's original values as hidden fields in the subfile.  The processing subroutine includes a loop for the subfile where it check for changed value(s) and does a normal update routine.  This fits nearly all scenarios for me as I keep subfiles limited in editable content. And yes, adding a processing subroutine does add code.

The other solution, for more involved edits, is a separate editing program outside the subfile program.  Adding a new customer, for instance, is not suited to subfiles.  Make one program with all the editing, validations, warnings, etc. in one place and let subfiles access it.  Let the deletions and additions happen there.

On 12/30/2019 2:34 PM, Patrik Schindler wrote:
Interesting. Using SQL, I assume? How do you handle record locking when loading a record for editing into a "details-screen"? Or do you count that part outside of your load-all? If you do, essentially stuffing a loop in 235 lines isn't too hard, I assume.;-)

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.