Glad you figured it out. Good job.


>I found it! Thanks.
>It was a textbox with a bit of innocuous code that said
>

>this.value = eval(this.controlsource)
>

>indirectly setting the table value.
>
>>Hi Don.
>>
>>As for the trigger firing when nothing changes, I expect that you'll find that nothing has *apparently* changed. I've had cases here when one of the programmers thought that setting the value of a bound control to the value of the field it's bound to was a good idea, and that make VFP need to update the record. It's not the act of changing a value that dirties a record but the act of setting it to a value, regardless of whether that value is the same is the field currently has or not. I suggest that perhaps you want to check the value of GetFLDState() as that will tell you which field(s) caused the record to become dirty. Then check controls that are bound to those fields and code that references them.
>>
>>Ian Simcock.
>>
>>
>>
>>>Maybe you can help with a related issue. Several of the tables in the dbc have update triggers set to call this logging routine. Something is firing the update trigger whenever the record pointer is moved even when no edits have been made. In my controlled tests this should not happen. I have searched the entire project for explicit tableupdate code and can find none that should be executed with a simple move of the record pointer. Can you help me figure out what is causing the trigger to fire? Debug is no help.