Data fields with auto-enter calculations will not update correctly if one of the values referenced comes from a field in a related table if that is the value that is being updated. That might explain why it's not updating correctly. You'd need to either return it to a calculation type or use a script trigger set on the referenced field to run a script to update your calculated field's value each time it is changed.
Any searches being performed that take extraordinary lengths of time are usually due to referencing a field that is unstored, from a related table or which has a corrupted index.
If you think you have a corrupted index, you can save a copy of your file with the clone option and then import all your data into this clone. The import process will rebuild the indexes of all your fields during import. You can also turn indexing off for a field, exit manage database, then return and turn it back on to rebuild the index of just one field--the trick here is to correctly figure out which field's index to rebuild.
We returned the field back to the calculation type, and rebuilt the index, by switching it off and back on. Now seems to be working ok, searches are fast, no more hanging.
Thanks a lot Phil.
If you have FM Advanced, you can also run File > Recover and go to Advanced features (added new in vs. 10 I think). Specify 'Copy File Blocks as is' and uncheck everything except 'Rebuild Indexes now.'
Using Copy File Blocks as is would be the only way I would suggest re-using a file which has been recovered. But this is a quick way to rebuild indexes on all fields.
Thanks LaRetta, good to know.
Ditto and a thumbs up.