Re: InteractiveChange and ProgrammaticChange Oddness

Author: Ken Dibble

Posted: 2016-06-15 at 13:20:20

>>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 VFP

> lost 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 and

> this.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

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/EE.01.07436.DDB91675@cdptpa-oedge01

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2016 Ken Dibble