Ok, then you can always do something like this :

declare @Results table (MyIdent int identity (1,1), fields...)

Insert into @Results (Select ....)

Select * from @Results

Or you could do some acrobatics...

Please do not cross post. We all keep track of all the new questions on all the discussion forums.

My answer has already been posted there.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=155717

You can use the TRUNCATE TABLE temptable to delete ALL the rows from the temp table before inserting the new data.

Just out of curiosity, why would you have a table system that has tblEmploye_101, tblEmploye_102.... instead of only 1 table?

it would look something like this :

Update MyTable set AlteredDate = case

when td = 'N' then dateadd(d, -2, ed)

when td = 'I' then dateadd(d, -1, ed)

else ed

end

I would try to run the profiler and then try to do an update.

Then I would grad the command from the profiler that fails to update and run it in...

I still don't think it's a good idea. If an application needs a db, I don't see why it shouldn't have one of it's own. I know I...

Well aside from recoding 69 apps (client and server side) to change the db connections and all the tablenames/view names and everything related too that. Not much... maybe just...

I just scripted and sp from QA and look at the first few lines

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

CREATE PROCEDURE [dbo].[AjouterProduit_CopyFrom] @NewCodeProduit as varchar(21), @NoProduit as int

AS

....

GO

The blank line...

No I don't mind. As long as the headline read something like this :

Capt. Carp outwitted by a 10 months old gold fish.

Or anything among those lines

Might not seem like it but I have other things to do in life...

Maybe in the year 2010 I'll be there.

I think I'll stick to a shorter name...

I'll call you Capt. Carp. from now on.

I'm assuming that my answer will work because the commas will actually make 4 records instead of 1... hence that might very well be the cause of the too many...

BTW this is only the tip of the iceberg. Once you understand how powerful and dangerous sql injection can be, you go out of your way to avoid it...

Sorry carpal tunnel... I'll try to find an harder solution next time .

BTW Antares had already pointed in the direction of the ms proc......