Yes sir, it is.

The COMPLETE code is over 1500 lines long, and a whole lot of it isn't relevant to our conversation. Plus, I can't post it due to intellectual property laws. What...

No, that's not the whole trigger. Other parts of the trigger just figure out what other variables need to be set to - but they've been in place for a...

Okay. Here's my actual code. What I'm doing is building an interface between two systems, and I'm setting patient disease indicators in one system based on data received in a...

Okay. Here's my situation. I have a function that accepts as a parameter a field that is a comma-seperated value. That function returns that data as seperate rows. So, if...

I thought we fixed that already?

You know what...never mind, this is becoming entirely frustrating. It can stay inefficient.

I just ran your script and mine on the exact same set of data? I'm confused.

No, the data still doesn't match up, and I'm getting an extra day out of it.

Yours:

2011-03-01 00:00:00.00011914592186

2011-03-02 00:00:00.000132214219814

2011-03-03 00:00:00.000107165319510

2011-03-04 00:00:00.000000046

Mine:

2011-03-01 00:00:00.0001281475212011

2011-03-02 00:00:00.0001412157191310

2011-03-03 00:00:00.0001121667191415

Was out of the office over the weekend. I will try your fix. The types just determine whether the event was an orderly or transport event. The only type that...

I changed the CASE statement for shift because it was reporting times prior to 06:30 as 1st shift - that's actually third shift (first doesn't start until 6:30). It also...

The data is closer now, but still not quite the same.

Here's how I modified the original code:

DECLARE @startDate datetime;

SET @startDate = '2011-03-01 00:00:00.000';

DECLARE @endDate datetime;

SET @endDate = '2011-03-03 00:00:00.000';

SELECT ...

Wait, I think I'm on to something. A little more messing around here oughta fix it.

Hey, I just noticed something. Check out the last field in each of your rows compared to the first field in each of my rows. They match.

There's going to be an awful lot of it...you sure you want all of it?

There's 700 rows in that time range with the appropriate [type] field that we're looking at...

Okay, now I'm getting a table back, but the data isn't correct.

From running my clunky procedure for, let's say the first three days of March, I get this:

(Columns are Date,...