AnsweredAssumed Answered

ODBC update doesn't sync correctly with shadow table if done from trigger

Question asked by jjbong on Jan 28, 2011
Latest reply on Feb 2, 2011 by jjbong

Like • Show 0 Likes0
Comment • 4

Title

Post

Using FileMaker Pro 11 with MySQL.

I set up a trigger on data modify (the modified data was in a shadow table). The triggered script did an update to a different MySQL table using ODBC, but the shadow table in FileMaker didn't reflect the updated data (it was all added data, not updates to existing rows - it just didn't see the new rows). I verified that the new rows were there in MySQL.

I changed the interface to run the same script from a button on the window, not from a trigger, and it worked fine.

Not a problem for me at this point, as I've reworked the interface so it works. But I thought I'd post the problem.

No one else has this question

Outcomes

bcooney Feb 2, 2011 12:31 PM

Interesting...what if you added a Refresh Window to the triggered script?

Actions

jjbong Feb 2, 2011 1:48 PM

Tried that, also Commit Records, and even going to a window that had nothing to do with the affected tables. None of it worked. But taking it out of the trigger and invoking the same script with a button worked.

Actions

philmodjunk Feb 2, 2011 2:49 PM

Did you also try Refresh Window with the Flush cached external data option?

Actions

jjbong Feb 2, 2011 3:27 PM

Did that too. This is what I do normally when I update through ODBC - Refresh Window with Flush cached external data, and commit records. In every other case, it does the trick.

Actions

4 Replies

bcooney Feb 2, 2011 12:31 PM
Mark Correct
Correct Answer
Interesting...what if you added a Refresh Window to the triggered script?
Like • Show 0 Likes0
Actions
jjbong Feb 2, 2011 1:48 PM
Mark Correct
Correct Answer
Tried that, also Commit Records, and even going to a window that had nothing to do with the affected tables. None of it worked. But taking it out of the trigger and invoking the same script with a button worked.
Like • Show 0 Likes0
Actions
philmodjunk Feb 2, 2011 2:49 PM
Mark Correct
Correct Answer
Did you also try Refresh Window with the Flush cached external data option?
Like • Show 0 Likes0
Actions
jjbong Feb 2, 2011 3:27 PM
Mark Correct
Correct Answer
Did that too. This is what I do normally when I update through ODBC - Refresh Window with Flush cached external data, and commit records. In every other case, it does the trick.
Like • Show 0 Likes0
Actions

ODBC update doesn't sync correctly with shadow table if done from trigger

Title

Post

Outcomes

Related Content

Recommended Content