When I am searching for someone and I mark it to search "exactly as marked" it will bring up all different names, places, etc.?
@Charlene Sparks 91786, Although I have seen this problem in the past; I have tried several searches using the "Match exactly" option, and cannot reproduce the problem that you have described. If you could share the search names, places, etc that have returned different names, places, etc, we might be able to give you a better answer.
It has happened often, with many different names and places so that would not help you, maybe it is in my computer, but when I go back to check if it is still marked it is still marked. For some reason I find familysearch.org difficult to use at times. I really miss when RootsWeb was loaded with information - and so was USGenWeb and GenForum. There were so many really helpful sites before Ancestry gobbled them up, now they often comes up "error 404" when you try to use them. At 86 I cannot afford to pay ancestry on a fixed income. Thank you anyway.
"For some value of exact that I am not familiar with" was my phrasing, as I recall. My problem turned out to boil down to alternate placenames.
I don't recall this problem happening with personal names, but I may simply be blocking the awful memory or something.
I do continue to be utterly baffled by FS Search's insistence that Nyiri is not a match to Nyiry. (This is not with the exact box marked or anything. Just a plain, general search, where these EXACT HOMOPHONES should come up right at the very top of the list.)
I wish now I had kept a note of the example I encountered yesterday. I made an "exact match" search, specifying an English county, but was still presented with results relating to places hundreds of miles away. This does happen to me occasionally and I have never been able to figure out why the FamilySearch programming does sometimes lead to these baffling results.
One "tip" - especially with place names - is to add a wildcard after the location. When I have searched for records that relate to "Sunderland" I have received "Nil" results, but inputting in the format "Sunderland*" makes all the difference. If there are multiple places with the same name in the database, I'm told "my" Sunderland (in this example) is too far down the list for program to produce the correct results, so using a wildcard at the end (or inputting "Sunderland, Durham" instead) gives me the desired results. In basic terms, you just have to "think like a computer"!