Please mark this thread as [RESOLVED] in the OP title.

@Techs Errata: Suggest you add a Result Name "sort key" to the RS pages which will certainly help viewers to find the one needle in the sometimes huge haystack of results listed. Also, the Sent Time sort, which appears to be the default could use a secondary key sort on the result name. If results are sent at the same time, you see those with same time stamp [up to the second, sub second meaningless to me and anyone], in some random order... a sample of a set received on one host appearing 'as-is' on mine: 439-63472 appears before 63386 which appears before 63405 but all have 13:58:30 as the sent time.

OET1_ 0000439_ xEBGP-S_ rig_ 6346_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 6341_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 63320_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 63472_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 63386_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 63405_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 63485_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0
OET1_ 0000439_ xEBGP-S_ rig_ 63420_ 0-- 3113135 In Progress 3/16/15 13:58:30 3/26/15 13:58:30 0.00 / 0.00 0.0 / 0.0

Thanks for your consideration.