Nice work MickyT. That does the job!

Hi Erland,

My apologies for not being clearer about the current / desired business logic.

Current Business Logic: 'Ord' is the sequence of events for the 'Name' & 'InOut' fields. The DuplicateRow...

capnhector you got it! Thanks so much for taking the time to understand and provide exactly what I was looking for. 😀

Ok I know you guys are trying to understand, so I'm going to try to be as explicit as possible.

DECLARE @data TABLE (Record int, GroupName varchar(50), History_Order int)

--First...

Hi Sean,

From the first DataSet

For the 1st DataSet ..

/* == RESULTS ==

Record GroupName HISTORY_ORDER Consec

300037 GroupD 1 1

300037 GroupD 2 2 <--2nd Consecutive occurance of 'GroupD'

300037...

Solved this myself.

There were a few key discoveries on the way.

Right click > Dataset parent > Show Hidden Datasets .. allowed me to see the query behind the SSRS...

Thanks for your reply.

Still a bit stuck here. I haven't found a way to use the 'MS OLE DB Driver for Visual Foxpro' to access memo/.dbv files, including using the...

I disagree that triggers are outdated. Even with the new functionality in 2008, there are occasions with vendor software where a business requirement simply cannot be met other than to...

Thanks for your response Michael. Any pointers on common mistakes / things to avoid when configuring replication?

My understanding is that there have been inherent issues with transactional replication (at least with SQL 2k) where the data is transferred to the replication database and no error is reported, but...

Howdy,

I've had another go at this and have discovered that I only needed a delete trigger. The syntax and all checks out alright, but the REP_SESSIONS_HISTORY tables isn't updating with...

Thanks PW. I had a feeling splitting the trigger was the way to go. I had contemplated a SET based approach but fear I gone off course. The application keeps...

Hi Daryl,

I am contemplating something very similar and would like to hear if anyone out there has gone through this exercise (successfully) before.

For scenario 1:

00456633  NULL

00458176  NULL

00461166  NULL

For scenario 2:

00456633  NULL

00458176  2005-08-01 13:41:54   Resolved     1121646538

00461166  2005-09-07 09:49:02   Resolved     1115274260

For scenario 3:

00456633 2005-08-26 14:02:07  Completed  1125026327 

00458176 2005-08-26 14:59:19  Reassigned 1124951416 

00461166 2005-09-15 13:15:00  Reassigned 1126225239 

In summary:

For CallID '00456633', there...

That's basically right. Unfortunately I need to mangle resolvdatetime into an additional column 'CaseResolvDatetime'. HeatSEQ looks to be like an index number i.e. whenever any CallID is updated/created, this is incremented by one. The...