make sure to use the "on error" on your activex scripts too

Some systems I have "inherited" had multiple Colums primary keys (4-5) and I was task to speed some of the code! One of the shortest solutions to get it going...

declare @t table (

 tid int,

 tname varchar(5)

)

INSERT INTO @T (tid, tname) VALUES (1,'HI')

INSERT INTO @T (tid, tname) VALUES (2,'Ho')

INSERT INTO @T (tid, tname) VALUES (3,'HI')

INSERT INTO @T (tid, tname) VALUES (4,'Ha')

INSERT...

Ok a primary key(pk) should be INVARIABLE with time. Sometimes it happens that what you thought it could be a good pk candidate is not anymore and you may ended...

Have a look at Linked Servers in BOL

thanks god those deals exist otherwise I would have been kicked out of my job

I said Nested Triggers  I should have said Recursive Triggers which by default is disabled

but even  if...

Or:

Declare @period int

SELECT @period = 3

Select (Case

 When @period = 1 then Acnt01

 When @period = 2 then Acnt02

 When @period = 3 then Acnt03

 When @period = 4 then Acnt04

 When @period =...

On your post the last line is :

...price' execute (@query1+@query2+@query3+Query4)

shouldn't Query4 be @query4?

I am not sure of your table structure or relationships there but this is a shot:

SELECT DISTINCT

            dbo.MySupportFiles.FileID,