Hi Tamar,

Thank you for your input.

1. I agree with the "No code in Click" and "No direct call to" conventions. I inherited this code and it is as it is, right, wrong and so on. Where it warrants, we're factoring things out. Moreover, we're going to be creating a completely new version from where we'll start over again with coding standards and best-practice. Until then, it is as it is. :-)

2. Thank you for pointing out the argument. I get tunnel vision and fail to read all that is there to read. I will look at the documentation on BINDEVENT and look for how it applies.

3. I discovered the REAL thing that was going on (I think). In earlier posts I thought I was observing VFP trying to handle multiple threads. Further investigation shows that the GPF was not happening because of threading but because of potentially stepping beyond the nested-iteration threshhold in VFP. I have looked at the logs produced at error-time and I noted hundreds of "GOTFOCUS" entries, which leads me to think VFP in production was complaining the only way it could: GPF.

Again -- thank you all for your kind responses and help! It is very much appreciated.