I am afraid you are right. I reviewed the relevant help topics, and they are, indeed, quite clear, but I had previously overlooked them. I will have to change the options in my system (back to "key and modified fields"), and see if it works.
With so many fields, the question arises if your tables are normalized. But even with normalized tables, you sometimes need many fields.
I don't know how to solve this situation; I will continue investigating.
For now, I tried to make the dilemma clear, in Thread #
960857.
Off-topic: You might be interested in this temple, which is being built near your city:
http://news.bahai.org/story.cfm?storyid=223or
http://temple.cl.bahai.orgSaludos,
Hilmar.
>I used optimistic table buffering (5), and what I did was to compile the application into an EXE, and open two instances of the EXE with the same form.
>
>I put EXE1 into edit mode, go to EXE2 and put it in edit mode, make changes in several records (of the child table in a one to many form), go to EXE1 and make changes in the same records, go to EXE2 save changes, go to EXE1 and save changes (which overwrited changes in EXE2 without complaining).
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)
