A user had several crashes in a row yesterday in the same unshared database that I have reported earlier. I continue to search for ways to avoid them. I think, but am not certain, they occur when the first assignment statement in a procedure is reached. Yesterday, the assignment came immediately after an addrecord statement. (The procedure adds a record and proceeds to assign values to several fields.) I wondered if this could be similar to the problem of opensecret followed by a variable definition, where it appears to me that one statement has not completed before the next line of code is executed. (Earlier I was suspicious that there was some connection between a find statement followed by an assignment, but never proved that nor ruled it out.)
In the addrecord / assignment case, it has worked hundreds of times, but then seems to fail several times in a row. On at least two occasions, I had added console statements to try to diagnose where the crash was occurring, and the crashing stopped after the addition of the console statements surrounding the assignment.
So I thought intentionally introducing a delay after the first addrecord statement, which I am going to do with the code that I posted in the PanX feed a few minutes ago, might eliminate the crashes. Do you have any reaction to my idea?
BTW, I assume the smallest delay I can create with a timer is 1 second, i.e. no fractional seconds.