This whole thread is not to cast stones at Jim and his team. I understand that most of the programming involved with the new system is beyond the arithmetic of the cal constants, elapsed counts and % difference calculations. Also that a lot of work is required to accommodate all the perturbations that can occur with obtaining the data and processing that simple arithmetic. The data for things like collaboration, segments and course adjustments looks like all the normal measurement data, but requires special handling by the program. I am sure that Jim and his team will develop a way to accommodate these perturbations. As soon as he does, we will think of new twists for special cases that will require more programming.
In the meantime, I have 2 measured courses that crash the system and 5 more to measure. A workaround would be appreciated.
I also now understand that maybe my single data entry person idea may not work if the collaborator's data is somehow not used. As of now, the person who originates and finally submits the certification request must sign out of the system and the collaborator must sign in separately to enter the collaborator's data, then sign out. The originator/submitter then signs back in to complete the Measurement Comparison and Application for Certification screens. Maybe these 2 gaps have something to do with the loss of the collaborator's data, as a single data entry person capability would eliminate the gaps.