Why not just use ROW_NUMBER() and then add a constant to it and do the whole update in one go? I don't think you need a cursor for this...

Would that make it too easy? (StudentID, LockerID, StartLease, EndLease) or similar?

Isn't this as simple as

School--(1,M)--Locker--(1,M)--LockerAssignment--(M,1)---Student

and

LockerAssignment--(M,1)--SchoolYear

From that you can join the tables and get all the current locker assignments etc.

You can't test your SQL properly, because your table doesn't contain the right records. I added a new record to the table so that both CID and MID are both...

Proper punctuation is a beautiful thing. Why no semi-colons at the end of your statements?

This worked for me:

--Create Test Table

CREATE TABLE [dbo].[Null_Table](

[CID] [int] NULL,

[MID] [int] NULL

) ON [PRIMARY];

GO ...

I have both editions of that book. That was the first really good book I found on DAX.

Somewhere here I have F&R's book, which is a bit mind-blowing, but they're...

You mean destroy the RBAR side, the side that's good at writing cursors and such?

Martin,

That's what I was afraid of... My brain might explode.

you know you're in for a rough ride when Ferrari & Russo freely admit that "DAX is hard"... uh oh.

I think that will work... Gotta re-read that part of the book. A few times. and then try it, and then read a few more times. And then maybe read...

If the reason for your loop is to implement a running total, why not just use a Window function and do something like

SUM( <column to be summed> ) OVER...

Since your UDF returns a table, you could probably use CROSS APPLY to pass values from the other table (the source for the two parameters) and then return the whole...

Oh okay. Thanks for the clarification. I guess I should learn a little MDX eventually... just so much to cover and so little time! (and not enough brain cells to...

Oh, so from a user's perspective, it's effectively the same... thanks!

Why not use a For Each file loop and then use an Excel connector and insert that way?

You probably need some serious normalization of the data you're importing. 255 columns...

Okay, let me approach this from a different angle, and maybe I can think this out.

The sale would always be associated with a given customer and the salesperson at the...