<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - BeforeUpdating and AfterUpdating events are not firing when records are edited in a Table Control"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=107839#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - BeforeUpdating and AfterUpdating events are not firing when records are edited in a Table Control"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=107839">bug 107839</a>
from <span class="vcard"><a class="email" href="mailto:BridgeportContractor@gmail.com" title="Howard Johnson <BridgeportContractor@gmail.com>"> <span class="fn">Howard Johnson</span></a>
</span></b>
<pre>WORKAROUND: To detect record edits use `After Record Action` in the form's
underlying record. This workaround comes from Jim K. here:
<a href="https://ask.libreoffice.org/en/question/139867/base-any-workarounds-for-tables-broken-afterupdating-beforeupdating-events/">https://ask.libreoffice.org/en/question/139867/base-any-workarounds-for-tables-broken-afterupdating-beforeupdating-events/</a>
`After Record Action` fires when any record addition, deletion, or update is
made.
`After Record Change`, fires when any record *motion* occurs, i.e. moving from
one record to another.
NOTE: This does not answer the original question here as to why or what the
`After Updating` event does, or does not do.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>