our workflow uses a new point number for the second time something is measured to in the field. this way we can check any misclosure. then in tbc we change the point numbers to the originally tied number and merge the points. you can tie with the same number in the field but will need to be aware that you will either average the two ties and can check misclosure then or you can store another observation to the same number and i think Access software will default to the original measurement for any computations for that field file. this saves the hassle of merging points in the office.
running a point derivation report on a point in tbc will show what measurements have been made to that point, but i would say it is not obvious how the observations are organized because they are divided up with a special tbc name assigned to each measurement.
we typically do the same with rtk ties to conventional points as well, or vis versa(rename and merge them). then use the network adjustment and not the traverse adjust command, usually fixing our base station location.
------------------------------
ian bissonnette
------------------------------