https://bugs.documentfoundation.org/show_bug.cgi?id=68153
--- Comment #20 from Howard Johnson <[email protected]> ---
(In reply to Lionel Elie Mamane from comment #18)
> That was not my question. Read my question again.
Ok, I see you ask a very excellent question!, one that will lead you to the
solution in fact...
The answer is a riddle: neither, and both, but timing is everything.
When the user moves the focus after editing a FK (individual field) not just up
or down, but also left or right, the query needs to update the pointed to
record and re-display the line, thus updating the other fields as necessary.
So then if another non-FK field or several are edited, the edits occur in the
correct sequence (timing).
>If edit FK-field
>Then update query before moving to next field
In other words, the query GUI is not a line editor except in the simple case of
a simple query of only one table.
In a query of a related records the query becomes simple fields and link
fields, and each need to be treated differently. Editing link fields
immediately causes certain parts of the query to update. Editing non-link
fields only update the underlying record when up/down record motion occurs.
I didn't think of this myself; I looked at how Access did it. I had been using
it so long I didn't even know how it worked till yesterday, I just knew that it
worked.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
