Thanks Sue - you reminded me that I did the exact same workaround when I confronted this problem before. I too am curious about the cause of the problem. It seems like something is wrong. Good to know someone else had the experience though, perhaps it's a Filemaker weirdness and not a corrupt database, which is my biggest worry. Terry On May 12, 2011, at 6:59 PM, Sue wrote: > I have had some troubles with Find in calculation fields in the same > configuration of software you are describing. > > In my case, performing a find on a calculation field seemed to work > at times for me and other users, but at other times it would cause a > spinning ball and then crash the file. > > I thought this might have something to do with how many people were > using the database on the server and possibly attempting the same > find at the same time? Just guessing. > > I ended up working around the problem by scripting a replace to > periodically enter the calculation results in a text field, then > having users do their Finds in the text field rather than in the > calculation field. > > That solved the immediate problem of locating the records needed at > least, but I would be interested to know how to ensure that use of > Find in a calculation field won't cause such problems. > > Sue > > > On May 12, 2011, at 6:41 PM, Terry Teitelbaum wrote: > >> Does anyone know why the Find function would not work on some >> fields? I've searched online and cannot find anything relevant. >> >> I am using FM 11 Advanced on a Mac and am accessing a file hosted >> on FM 11 Server Advanced on a PC. >> >> The fields are part of a duplicate calculation and message. >> >> I have a self-join on a field "RouteStop" >> >> [RouteStop is a calculation field, text, indexed] >> >> Then I have a field: routestopdupecount: unstored, >> Count( routestopdupe::RouteStop ) >> >> And finally, a message field, Dupe Alert Route Stop: >> unstored, calculation, text: >> If(routestopdupe::routestopdupecount>1; "There is more than one >> customer with this route and stop";"") >> >> The message works properly; it shows up in the field of records >> with a route and stop the same as any other record. But the problem >> is when I want to find these records. >> >> In find mode when I enter * in the Duper Alert Route Stop field, at >> first I got a message that no records matched the criteria, and now >> it returns all but 14 records (in a database with 2178 records), >> and not the correct records. When I enter =, it returns a few >> records but again, it's not a correct found set. The same is true >> if I enter >0 or find matching records on the field in a record >> with the message. >> >> I've tried searching on the routestopdupecount field with >1 and it >> doesn't return any records. Same is true if I enter T or even the >> entire message copied and pasted from a record with the message. >> >> Could something be wrong with my database? >> >> Any help or insights would be most appreciated! Thanks. >> >> Terry