I never thought of doing that but it may work. I'll play around with this and let you know how I get on.

Thanks for the suggestion!

I'm not sure that is going to help me. I only want to ignore two specific rows if there is a row with a value of P001.

Thanks for the reply. Just in case there is any confusion, I want all of the rows to be inserted into the table which has the trigger applied, but if...

Ok thanks for the advice on this. It looks like I may have to get back to the drawing board on this one.

I'll let you know how I get on.

The part of our application this refers to can insert more than one row at a time. Are you saying that even if the user selects say 5 items from...

Here is the table script:

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

CREATE TABLE [dbo].[wipTest](

[caseID] [int] NULL,

[wipCode] [varchar](10) NULL,

[shortNarrative] [varchar](1000) NULL

) ON [PRIMARY]

GO

SET ANSI_PADDING OFF

I actually have another table in my live...

Sorry if I wasn't clear. If I was to use the following insert statement on the table which has the trigger applied:

begin tran

insert into wipTest values (123, 'P001', 'P001 text')

insert...

If you only need to know the column names then why don't you use select * from Employees

I'm planning on only using the reporting server to store and publish the reports. If that means I can use the server as a witness as well then great.

Thanks John. But just out of interest why would I be getting that error?