Can you elaborate on point 1? I use many triggers in my ESS SQL database in conjunction with Filemaker 11 and 12.
Point 2, you are absolutely correct. I have been petitioning FMI about this since the release of ESS. More voices are needed to get them to put the time into this. I believe they were very fixated on the UI enhancements with V12. It seems many of the features I care most about are towards the back of the list. ESS, IWP and real enhancements to the reporting capabilities of Filemaker. We just have to keep beating the drums and hope things will improve going forward. ;-)
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TABLE [dbo].[InsertTriggerTest](
[Datum] [int] NULL,
[Comment] [nchar](10) NULL
) ON [PRIMARY]
CREATE TRIGGER [dbo].[trig_Insert] ON [dbo].[InsertTriggerTest]
SET NOCOUNT ON
SET Comment = 'hooray' -- this is vaccuous, of course. In reality you would be inserting a record into a log table, for example.
In FM, make a relation to InsertTriggerTest and insert something. I get this:
I work around it by creating an AFTER UPDATE trigger and using a two-step FM process (inserting a record, then modifying it), but this kind of kluge always obscures things for maintenance people, and it leaves something which might break if FileMaker ever gets serious about SQL triggers.
I'm not up to date with my SQL Server triggers, but does this work with other applications?
What does the Set NOCOUNT option do?
Sorry to take so long to reply.