cterrell16 Posted August 26, 2016 Share Posted August 26, 2016 (edited) I have a layout that has a calculation field for my records. This calculation shows if an order is open or closed. Normally I can use the search feature and type open in that field to show all my open records. Just last week it doesn't search correctly. When I search for all the open records now it will bring up a lot of closed records and just a few open records. The calculation hasn't been changed and it works if you look at my records individually. This is my calculation. If(GetAsNumber(BALANCESHIP)=0;"CLOSED"; "OPEN") Edited August 26, 2016 by cterrell16 Link to comment Share on other sites More sharing options...
Ted S Posted August 26, 2016 Share Posted August 26, 2016 Is your calculation calculating properly? I mean if you look at the field does it show CLOSED for records that you really would consider closed? Link to comment Share on other sites More sharing options...
cterrell16 Posted August 26, 2016 Author Share Posted August 26, 2016 yes its working correctly. Except for when you search that field. Link to comment Share on other sites More sharing options...
cterrell16 Posted August 29, 2016 Author Share Posted August 29, 2016 Any ideas. I don't see how this could happen during a search. Link to comment Share on other sites More sharing options...
Ted S Posted August 29, 2016 Share Posted August 29, 2016 Sorry for the delayed response but maybe try turning off indexing on that calculated field and then turning it back on again to force FM to rebuild the index. Maybe the index got corrupted and no longer matches the field content. My other thought is to stretch the field out vertically on your layout to make sure that both the Open and Closed aren't values contained in the field. Link to comment Share on other sites More sharing options...
Lee Smith Posted August 29, 2016 Share Posted August 29, 2016 To add to Ted S’s suggestion, see this post I found doing a Google search for "How do you reindex a field in FileMaker" HTH Lee 1 Link to comment Share on other sites More sharing options...
Ted S Posted August 29, 2016 Share Posted August 29, 2016 Also look for really simple goof-ups. In the past I've been baffled by FM's behavior when I have made rookie mistakes like binding the wrong (but similar) script to a button or having nearly identical fields in the DB and searching one while looking at the other. Think about the problem as if you had to explain it to somebody who had no experience with it. I can't count the number of times a user will call me with a problem and as they are explaining it to me it suddenly occurs to them what they are doing wrong. One more thought: Is your field a true calculated field or is it an auto-entered calculation? Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 2790 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now