a user brought this 'interesting' behavior to my plate this pm.
there is a form called 'Protocol' which has nested w/in it a sub-form called 'Tracking'. the 'Protocol' (parent) form is linked to the sub-form via a field called 'IRB#'.
the tables of each have the forms' same names and the pk of 'Protocol' is 'IRB#' and the pk of 'Tracking' table is (composite) 'IRB#' AND 'Date'.
in looking at the underlying 'Tracking' table, things are copacetic, however the user told me that when they entered a record in 'Tracking' with a date that was not in the chronological order that had preceded it, that it continued to remain in the same (last row)!
graphically, the form for IRB# ABC1 would look like this after the user entered the final record,
IRB# Date
ABC1 01/02/03
ABC1 01/02/04
ABC1 02/03/04
ABC1 03/29/04
ABC1 03/24/04 <-- why does this not show up above 03/29/04 on the form?
“The philosophy of the school room in one generation will be the philosophy of government in the next." --- Abraham Lincoln
there is a form called 'Protocol' which has nested w/in it a sub-form called 'Tracking'. the 'Protocol' (parent) form is linked to the sub-form via a field called 'IRB#'.
the tables of each have the forms' same names and the pk of 'Protocol' is 'IRB#' and the pk of 'Tracking' table is (composite) 'IRB#' AND 'Date'.
in looking at the underlying 'Tracking' table, things are copacetic, however the user told me that when they entered a record in 'Tracking' with a date that was not in the chronological order that had preceded it, that it continued to remain in the same (last row)!
graphically, the form for IRB# ABC1 would look like this after the user entered the final record,
IRB# Date
ABC1 01/02/03
ABC1 01/02/04
ABC1 02/03/04
ABC1 03/29/04
ABC1 03/24/04 <-- why does this not show up above 03/29/04 on the form?
“The philosophy of the school room in one generation will be the philosophy of government in the next." --- Abraham Lincoln