AnsweredAssumed Answered

ExecuteSQL working sporadically with some T-SQL script triggers...

Question asked by TomEdge on Feb 15, 2018
Latest reply on Feb 16, 2018 by beverly

FileMaker Server 16

Multiple ODBC driver versions (13.1 Latest attempt)


FM GO performs script on server that has ExecuteSQL statement "UPDATE tblAttendance SET dtLogout = '2018-02-15 15:00:00.000' WHERE ID = 28342".


That table has a trigger that does a bunch of data updates on another DB on the SQL Server.  I recently updated the trigger code and have found that it works sometimes and not others.  But either way, I don't get a LastExternalErrorDetail returned from the server or any error at all.


Stranger still, I can see the statement arrive in the server trace log and it appears to complete, but it hasn't.


If I copy the query statement sent by the ODBC driver and execute it in Management Studio it works fine.


If I send the statement from another application using the same ODBC driver it works fine.


Only when I send the statement from FileMaker does it fail to complete and fail to return an error message....


Any ideas?