you need to decide what aggregate you want for the other fields. If you want the highest age and salary for each name and email combination you could try...

Goodguy, look at my earlier post. If you do not specify a length for the parameter @col it defaults to a length of 1. The value 'Oct' is...

As everyone else has said formatting is best left to reporting tools but this will do what you want.

declare @delim1 varchar(30),@delim2 varchar(30),@delim3 varchar(30)

select @delim1 = '---------------'+ char(10) + char(13)

select @delim2...

you need to set a length for the @col parameter. otherwise it defaults to 1 and all you get is 'O'.

exec sp_executesql @sql,N'@oct decimal,@col char(3),@sep decimal',@oct = @oct,@col=@col,@sep=@sep

Are there only four values in the look up table or are there more? Will there be more in the future?

That is what I usuallly use but it doesn't provide the pretty, formatted (albeit truncated:P) output and a nifty wizard to input the variables.

MattieNH (10/4/2007)

---

mrpolecat (10/4/2007)

---

Are we using the same QA? I would love to know how you get QA to build the query for you.

I bring up the Object...

Maybe a dumb question but

Are you getting the same error on the production server that you got in development?

Are we using the same QA? I would love to know how you get QA to build the query for you.

Or maybe not if it plays tricks...

I expected there to be a PK and then would have selected distinct PK to get the actual rows. I guess with a large table your way would be...

That answer is on the board here somewhere , I don't remember the syntax. Do a search for top nth and you should find it.

Select t1.*

From History t1

join history t2

on t1.DialID = t2.DialID and

t1.ProjectID <> t2.ProjectID

and to check pm's there is a link at the top of the page that says

Control Panel 0/1 Messages

Click on Messages.

you don't want to highlight the cell with the data in it. You want a blank cell in the same row.

In the blank cell in row 1 type

=right(a1,7)

this will...

I don't think it is your odbc driver but here is the connection string we use

conn_tb = "DRIVER=SQL Server;Address=10.10.10.10,1433;DATABASE=applications;SERVER=10.10.10.10;UID=username;PWD=password;"

Is your mdac up to date?