Seth,

Thanks for the info and code...

John

Of course I am doing it that way Jeff... none other would do... it takes about 15 minutes to do the Approx. 4MILL rows...

I think I am getting it... basically...

Nothing like that at all, at least they didn't require that yet...lol

[A].[PMT_FREQ_MULT] = @PMT_FREQ_MULT: this tells me which DATEADD to use in the CASE Statement M Month, D Day, Y...

I never saw the attachments... doh;

ok, so i ran a couple of the ID's with variety thru the fuction I posted early... this should give you a visual of what...

Ok, row 85 is a new ID, 101 and 102 are new ID's and so is 103 ending @ 111...

when i get the data, it's not ballooned out like this...

I'm not given the Origination Date... I have a column AS_OF_DATE so we now when the table was created, I have the PREVIOUS_PAYMENT_DATE, NEXT_PAYMENT_DATE AND MATURITY_DATE.

Then we move forward from...

No, notice the if statements... if the date i pass in doesn't equal the end of the month then do something else.... and the other if...

I am getting dates that can start from the first, and be due anytime inbetween... not only that, they can be days apart, years apart...

I guess i made the wrong...

I am confused... the dates come to me as is... the one with a Nov Date started it's journey from

2008-10-31 00:00:00.000, and it came out right to Nov 30...

I ran both mine and your updated statement...

How do interpret the Execution plan??? or should I post this as new question?

mine a

mine b

C:\Documents and Settings\xjasn4n\My Documents\My...

Ok, so it's top down... thanks for that...

I try to avoid Correlated Query's... That is why the previous Update Example I posted for this question is done... its used here...

Yes Sir, for both the last Columns...

IF OBJECT_ID('tempdb..##PS') IS NOT NULL

DROP TABLE...

I have several different ID's, could have 1 ID with 10 rows another with 15 rows, etc...

This update statement is doing some setups to do an Amortization, so i have...

UPDATE TABLE1

SET

, @vEVAL = [COL3]

, @V1 = [COL1] = CASE @vEVAL = TRUE THEN 1 ELSE 0...