That is still happening irregularly but I can’t reproduce it reliably. Meanwhile, here’s a variation - in the same database that exhibited the original problem:
In the database, I record daily, both sitting and standing, my systolic and diastolic blood pressures and my heart rate. Entering the final value for the day triggers this procedure which tidies up, saves and closes:
As you can see, it sets up an endless loop which I can exit only by forcing a quit, even though there’s a
stop statement in the procedure. There are no other triggered procedures in the database. This behaviour is totally reproducible.
I don’t expect that anybody will have an explanation for this but Jim may be interested in looking at it. There again, he has more important issues to deal with.