Okay. I did Skype screen sharing with my coworker and worked through the setting changes (not incredibly computer literate). To both of our shock, this worked. Thank you, Paul. Turning off Lookahead, then repeating changes and confirmations to the same segment showed just a CM or 100% hit in the results window. No duplicates. As it should be. We turned Lookahead back on and it worked normal, with no duplicates, much to her surprise as well (can't stress this enough). It generally worked fine except a couple times after changing one segment, the same segment would show the previously confirmed edit, not the new one, but not as a duplicate. Just 100% match of an old hit despite confirm a new version of it. This was with Lookahead on, and I know that sometimes there's a lag with the search results so refreshing the view would fix it. I forgot how to refresh the results window (Ctrl something?) but changing the TM project settings a couple of times and it refreshed and worked again. Hopefully, in the future, this lag can be fixed confirming a segment will refresh the results automatically.

Side note: When not translating myself, I spend a decent chunk of my time troubleshooting for my coworkers... to the point where I take regular support tours to their workplaces to help, fix, teach, and refresh their memories hands-on. Despite my role as the ad hoc expert within the company, I would never have guessed that "resetting" lookahead would fix it. I often encounter problems that baffle me so I just end up apologizing on behalf of the software (it was my idea to use trados in the company so I feel responsible). So yeah, forgive the constructive feedback, but some solutions are not instinctive to me and even less obvious to my less computer-literate, Japanese speaking co-workers. 

Okay. I did Skype screen sharing with my coworker and worked through the setting changes (not incredibly computer literate). To both of our shock, this worked. Thank you, Paul. Turning off Lookahead, then repeating changes and confirmations to the same segment showed just a CM or 100% hit in the results window. No duplicates. As it should be. We turned Lookahead back on and it worked normal, with no duplicates, much to her surprise as well (can't stress this enough). It generally worked fine except a couple times after changing one segment, the same segment would show the previously confirmed edit, not the new one, but not as a duplicate. Just 100% match of an old hit despite confirm a new version of it. This was with Lookahead on, and I know that sometimes there's a lag with the search results so refreshing the view would fix it. I forgot how to refresh the results window (Ctrl something?) but changing the TM project settings a couple of times and it refreshed and worked again. Hopefully, in the future, this lag can be fixed confirming a segment will refresh the results automatically.

Side note: When not translating myself, I spend a decent chunk of my time troubleshooting for my coworkers... to the point where I take regular support tours to their workplaces to help, fix, teach, and refresh their memories hands-on. Despite my role as the ad hoc expert within the company, I would never have guessed that "resetting" lookahead would fix it. I often encounter problems that baffle me so I just end up apologizing on behalf of the software (it was my idea to use trados in the company so I feel responsible). So yeah, forgive the constructive feedback, but some solutions are not instinctive to me and even less obvious to my less computer-literate, Japanese speaking co-workers.