The following applies to all versions of VFP, and - I believe - both to local and remote view.
How should conflict management (in a multi-user scenario) be handled in views, when there are many fields in the underlying tables?
If the "SQL Where Clause includes" option is set to "Key and modified fields", it is possible that too long a SQL string is generated (as reported in Thread #
959751).
If the option is changed to "Key fields only", then there is no conflict management - the record will be saved as long as the key field didn't change.
So, how can we combine conflict management, with the requirement of possibly using many fields? Do we have to manually lock and compare oldval(), or something similar, before committing changes? Is this even possible in a remote view?
TIA,
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
