Does the function have to return a string. It would be easier if it was a table-returning function.

If it has to be a string, you could always count the nuber...

Could you please post the definition of your table, some example data and expected output please. I'm not completely sure from your description what it is you want.

thanks

Well this site's probably the best.

http://www.sqlskills.com

http://www.sql-performance.com

First, may I suggest you post in a more appropriate forum, like SQL Administration or SQL General. This forum is for discussion of the site's question of the Day, not general...

Pleasure, got nothing else to do right now.

(looks cautiously around for boss)

You can get variables out. I find, personally, it's the main use of it.

DECLARE @RecordCount INT

EXEC sp_executesql N'SELECT @RecordCountOut=COUNT(*) FROM sysobjects', N'@RecordCountOut INT OUTPUT', @RecordCountOut=@RecordCount OUTPUT

SELECT @RecordCount

It's like a stored procedure...

Use UNION ALL rather than UNION. There's no possibility of duplicates between the two queries.

UNION means SQL will take the two result sets, concatinate, then sort to remove duplicates. UNION...

And if you don't know all the columns and need dynamic SQL

B. Execute('Select @NEWVAL  =  ins.' + @FIELDNAME + ' FROM inserted ins WHERE ins.RegAudited = ' +...

Actually, come to think of it, the initial insert that you do to insert all the products is unnecessary. If there's a possibility that there will be products in Product_Forcast...

btw HTH stands for Hope that helps.

Close, but not quite.

Create the table sales and populate the years and products you want....

Why a gobal temporary table?

Why do you not know what database the table is in?

Could you expalin in a bit more detail the situation and what you're trying to do?

Select * from tbl

 where ID IN (SELECT ID FROM tbl WHERE transaction='1000')

 AND ID IN (SELECT ID FROM tbl WHERE transaction='2000')

Messy, but it'll work

If you're using temp tables in order to get values out of dynamic sql, look at sp_executesql. It lets you pass parameters to dynamic sql, both input and output parameters.

Triggers should be as small as possible. I shudder at the thought of anythihng (especially a trigger) that requires that many variables.

> is it the right way to programm the...