Here's the jist of it.....

DECLARE @myTable TABLE

(val1 CHAR(9)

,val2 CHAR(9)

,val3 CHAR(5)

,val4 CHAR(9))

INSERT @myTable

...

I found that my ASSUMPTIONS were wrong... LOL

I create a SQL Dataset/Command and ASSUMED that the parameters for that command are "linked" to the report when the Dataset is linked....

Might I hope that you always continue...

You just made it more complicated than it was. 🙂 It happens to all of us.

No need for CTE here. the pivoted columns exist as columns in the outer level so you can simply add them together there.

SELECT

OS

,Severity

...

The problem is that the line number is NOT a column in the source file.

I tested with a file of 10 million rows and it worked fine, but that's not...

I have a PK on the table, and the original file's line number is all that is important. That is, I'm not concerned how it is stored in the table,...

Emilio.Mendoza (7/8/2008)

---

Well for me I think this could be done in a very simple way, why don't you check at OS level when was the last time de MDF file...

Sometimes, just stepping back from the problem, walking around behind it and looking from the other side helps. 😀

You're close ...

DECLARE @mytable TABLE (IdentityKey INT IDENTITY(1,1), field1 VARCHAR(10))

INSERT @mytable

select 'test1' UNION ALL

select 'test1' UNION ALL

...

From BOL ...

.WRITE ( expression, @Offset , @Length )

Specifies that a section of the value of column_name is to be modified. expression replaces @Length units starting from @Offset of column_name....

Sure, create a Tally table and use the below function ....

(compliments to Jeff Moden)

ALTER FUNCTION [dbo].[split]

(@String VARCHAR(8000)

,@Delimiter VARCHAR(5))

RETURNS @RtnValue TABLE

...

I'm still not sure why yours isn't working, but the code below seems to get the correct results. 😀

ALTER TRIGGER [trUpdateBeginVacant]

ON [dbo].[propbut_mi]

FOR INSERT, UPDATE

AS

IF (UPDATE(DDELIVERED) OR UPDATE(DMOVEIN) OR UPDATE(DMOVEOUT))

...

jim.powers (7/3/2008)

---

I used FOR since that was how the examples were written. Plus the documentation says, "AFTER is the default when FOR is the only keyword specified."

It seems like it...

Change to ... ????

CREATE TRIGGER trUpdateBeginVacant

ON propbut_mi

AFTER INSERT, UPDATE

AS

...