Yes, here is a sample of what I am trying to complete:
Data (located in three different rows in the table):
ID DOB
1 01-01-1959
2 02-02-1959
3 03-03-1959
data needed returned in one row in my report:
client_id Name dob1 dob2 dob3
1 John Doe 01-01-1959 02-02-1959 03-03-1959
I sort to get them in the correct order. And, I have tried minimum ({client_dob.dob}, {client_dob.client_ID}) for my dob1, and nthsmallest (2, {client_dob.dob}, {client_dob.client_ID})for dob2 or nthlargest (2, {client_dob.dob}, {client_dob.client_ID})for dob2, and maximum ({client_dob.dob}, {client_dob.client_ID}) for dob3.
The problem I encountered is when I use nthsmallest (2, {client_dob.dob} to obtain dob2, it displays the same value as minimun (dob1), and the opposite occurs when I use nthlargest (2, {client_dob.dob}, {client_dob.client_ID}) to obtain dob2, it returns the same as maximum (dob3).