Well I thought I understood it until I ran the very last part...

I'm not seeing the connection just yet???

I've updated my code, still not sure how to repeat the process...

2 RESULTS:

12008-09-25 00:00:00.000483319.454163.763303.85236217137859.90763782863482459.5423621714163.768.454858333333330.08085

22008-12-09 00:00:00.000300003466.49401875133.164018753333.3326666.673333.338.454858333333330.0525

QUERY:

SELECT

[ID_NUMBER]

,[NEXT_PAYMENT_DATE]

,CAST ([CUR_PAR_BAL] AS FLOAT)AS [Begin Balance] --v_bal_before_pmt]-- THIS CHANGES DURING THE LOOP

,[XJASN4N].[fn_TOTAL_PAYMENT](XJASN4N.fn_RUNOFF_CONSTANTS([AMRT_TYPE_CD])

, CAST([CUR_PAR_BAL]...

I had to get something together that was legable for you all...

In the query off to the side i put what is constants...

for each result I need to then...

ok, so i put it like this?

SQLCMD -i Y:\ALLL\NewTrigger4ColumnUpdates\trg_I_tblRptLevel_AuditUpdates.sql -Q

even with out the -Q i get an error

Msg 170, Level 15, State 1, Line 1

Line 1: Incorrect syntax near...

So this is what mine would have to be? This is new for me, just want to verify so as to not break something...lol

Thanks,

John

SQLCMD -Q "Y:/ALLL\NewTrigger4ColumnUpdates\trg_tblRptLevel_AuditUpdates.txt"

The ON Clause is already done in each of the text files... below is the top portion of one of the txt files... as you can see everything is done...

This morning my boss went in and looks and saw most changes he made yesterday... it's like 1 out of 10 where something may not end up in the log...

I found the top portion and applied that to Jeff Modens Tally Table concept

See if it's what you want...

DECLARE @BASEYEARCHAR(4)

DECLARE @WEEKNOINT

DECLARE...

check out my post "UnPivot"... same concept, you just won't need the cross join and you'll use seperate CASE statements instead of 1 big one...

If I am correct in my assumptions, could you please post the schema of the table (table name, column names and data types) and the trigger code? Also please...

I get it now, thank you all so much...

"And remember the rule - never use functions on table columns in WHERE clause. "

Is this like the CROSS APPLY???

I didn't know that...

so if i made a tally table with less rows (below that of the highest date SQL server has) I could avoid the error that way...

I think i get...

I'm thinking my where clause (for months) was comparing

WHERE DATEADD(m,t.N-1, @DateStart) <= @DateEnd

would be equivilant to below

WHERE '2013-08-25 00:00:00.000' <= '2013-08-25 00:00:00.000'

thus when true...

It sounds like your saying that my where clause was followed and SQL stopped making rows, but continued on with the query any way???

below instead of going for months, i...

that would be if i didn't have a where clause right...

this was my where clause:

DATEADD(m,t.N-1, @DateStart) <= @DateEnd

It gave me the correct rows but errored as well???