Sorry, I don't have an answer, but a suggestion. If...

I have no experience with the PIVOT statement, but I did have one question for you. What do you get if you take the case statement out and just pull...

if object_id('tempdb..#totest')is not null drop table #totest

create table #totest(

clm1 int

)

insert #totest values ('5')

--begin tran

select * from #totest

commit

alter table #totest

add clm2 char(1)

select * from #totest

Here's what I came up with. A few things to note:

Getting the count of columns is done by uncommenting the section that does that, you'll see it down there...

The testing...

Have you considered using SSIS? The package contains the connection information. You would be able to accomplish the same thing (Excel to SQL) that you are using MSAccess for now.

Another...

I just tried this bit of code, both select statements run, and it gave me the same error as well. So I imagine that whatever you had after the statement...

Well, then it seems to me...

You did see the part about the possible duplicate sums, I hope. Just want to make sure that you have thought about the error that is inherent in my solution.

I have used a date table in the past. This would be an auto-generated table that had dates with week numbers etc. in different columns. I have a spreadsheet that...

Is this in SSIS or is the stored procedure itself exporting...

I'm afraid I'm the mechanic with all the broken cars. Would you really want me to help? 😉

Hmm, so the problem is fixed then?

Are each of these columns in the tblleveltolevelrel table?active,changeddate,changedmachinename

Or are they in the TempDelete table?

How many records do you get when you run each of the following statements?

SELECT tblLevelToLevelRel.Active,changeddate,changedmachinename

FROM tblLevelToLevelRel INNER JOIN

TempDelete ON tblLevelToLevelRel.GenLevelToLevelRelID = TempDelete.genleveltolevelrelid

Select * from tblLevelToLevelRel

What about tblLevelToLevelRel?