IF THIS.Value <> THIS.OldValue
triggered Error 107 ("Operator/operand type mismatch") in the InteractiveChange() method.
That is the first odd issue. I cannot figure out for the life of me how that could happen.
A VFP bug is possible. I had a case with aliases where VFPlost track somehow. This was in a loop where the loop could have executed thousands of times on the table. It was also in code that had run fine for quite a while.
What are the types and values of this.value andthis.oldvalue? Dump out that in your error handler. You might have a VFP bug, but you might have something you overlooked.
Have done, and if I'm still alive and not retired the next time it happens, I'll let you know what I find.
Thanks.
Ken Dibble www.stic-cil.org
At 11:20 2016-06-15, Ken Dibble krdibble@stny.rr.com wrote:
[Gene Wirchenko wrote:]
A VFP bug is possible. I had a case with aliases where VFPlost track somehow. This was in a loop where the loop could have executed thousands of times on the table. It was also in code that had run fine for quite a while.
What are the types and values of this.value andthis.oldvalue? Dump out that in your error handler. You might have a VFP bug, but you might have something you overlooked.
Have done, and if I'm still alive and not retired the next time it happens, I'll let you know what I find.
Next up: the mixed feelings should you find the cause. The satisfaction of having nailed it. The dissatisfaction that you had to.
The best I can suggest is to start suspecting everything. Start close to the problem and spread out as needed. That is what I did with my alias problem noted above. My code should have worked and usually did, but since it did not, I had to kludge it.
Best of luck.
Sincerely,
Gene Wirchenko
-
Gene Wirchenko -
Ken Dibble