Sara,

 your query, even if you try to do it from QA, does not represents the output that the poster requested

That is a presentation issue that should be done on the report designer of your choise. On SQL it will be just a matter of ordering by product name

It will reduce network traffic by not sending the count of affected records of each statement  back to the client (in a separated stream )

OK I have no data for testing but here it goes:

Select member_name, Sum( datediff ( d, SD, ED ) ) Total_Days 

from

(

--Find all islands

select member_name

 , startdate SD

 , (select...

Select @@rowcount -- after the Update, insert or delete statement

The N is just a way to tell SQL that the string is a UNICODE string object names in sysobjects are represented in nvarchar(128) (sysname) On systems where the collation...

Ok I had to do stuff and got a bit "side tracked"

If you need to really do this for more than 4 possible...

Another workaround is to use Table Datatype variables which are not affected by Transaction Handling statements!

Yep, You never know

Cuba, 30 yrs

Nope!!

You should not do that it is considered a bad practice and you are giving to "chance" the order of the columns. To be really in control you need to...

I doubt that!!! VBA can handle very very ... did I said very large strings

Can you post your vba Code?

INSERT INTO dbo.[Versuchsart] (

[SchaetzungID]  ,

[Nr],

[Bezeichnung]  ,

[Vorschrift] ,

[Lastenheft] ,

[Beschreibung]  ,

[Optional] ,

[Kombiniert] ,

[Zeilenart] ,

[AcVersuchsartID]  ,

[AcSchaetzungID]

)

select

[SchaetzungID]  ,

[Nr],

[Bezeichnung]  ,

[Vorschrift] ,

[Lastenheft] ,

[Beschreibung]  ,

[Optional] ,

[Kombiniert] ,

[Zeilenart] ,

[AcVersuchsartID]  ,

[AcSchaetzungID]

From

AuswahlVersuchsart

That Design is not very consistent in the sense of hadling "multiple columns" updates.

The two most used mechanisms are:

1.Simply insert the deleted and the Inserted rows with "OLD" and "NEW"...

Happy to Help