Patrik,

The way this is normally handled is to re-present any changed data back to
the user - with a message such as:

"This item has been modified since this screen was loaded - press F5 to
Refresh"

There are two main ways you can recognise that the data has changed:

- If your table has an audit timestamp (e.g timestamp last changed), that
you trust, you can store this as a hidden field on the subfile and compare
that to the database record before allowing update.
- In that absence of such an audit timestamp, you can store some or all of
the record before image for comparison with the (current) record before
allowing update.

Here is an example of the latter:

https://www.mcpressonline.com/programming/rpg/techtip-use-qualified-data-structures-for-checking-records

regards,
Craig

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.