Thank you for the post.
Try placing the search within double quotes like "firstname.lastname@example.org" to see if that makes a difference.
I suspect the use of the "@" (any one character) symbol operator in the find is the reason the search is failing.
Additionally, here is the help on use of operators when finding text and characters:
That worked, but what happens when I export the list to the newsletter editor who uses the email addresses to send the newsletter? Also, I have 520+ members, will I have to enter the quotation marks on each individual? Do you have any idea why this changed when I upgraded to 13? I had no problem when I was using version 5.
Thank you for the reply.
Please note: Report An Issue is intended for Reporting Possible Software bugs. Questions on how to work with FileMaker Pro should be posted in the FM Pro Forum Section. (See tab at top of this screen).
"what happens when I export the list to the newsletter editor who uses the email addresses to send the newsletter?"
I am unsure if I understand the question. I was not suggesting to add the double quotes in the actual field, but only when doing the find.
"will I have to enter the quotation marks on each individual?"
The purpose of using the quotes during the find is to request the exact text between the quotes; whereas, before (without the quotes) the program was looking for the email address and any single character in the place of the @ symbol.
"Do you have any idea why this changed when I upgraded to 13?"
A number of features changed or were added since version 5. For a full list of changes by version see the following:
I've used FileMaker since FileMaker Pro 2.5. FileMaker 5 and the latest versions of FileMaker all used the @ symbol in this way and the correct way to work around it has, to the best of my memory, always been to enclose the search criteria in quotes. (You do not enter your data with the email address enclosed in quotes when creating records and editing data, only when you are searching an email address field and want to treat the @ operator as a character in the search criteria instead of as a search operator.)
Thanks, I will try that and see if it works.
Thank you for your help. That works. I am 72 and not very computer literate, so I really appreciate your help.