Searches should occur in the snap of a finger. My guess is you are searching unstored calculation fields which don't use the index. As for your crashing when your computer goes to sleep, I have never experienced this issue but maybe someone else here can comment. Good luck!
Oh, I know what causes those slow searches, but because I'm frequently called upon to fix the poor work by other developers ("why is this search so slow?"), I tend to experience these more often than I should. I'm happy to fix a slow search when I encounter it, but encountering it always involves the aforementioned force-quit. Stuff happens, as the saying (sorta) goes; I'm just begging FileMaker to help me out when it happens – better tools to interrupt processes that have gone awry.
I know what you mean about fixing subpar work. Good luck!
1 of 1 people found this helpful
I'm happy to fix a slow search when I encounter it, but encountering it always involves the aforementioned force-quit.
If the file is not hosted on FMS then doing a force-quit like this could potentially damage the file and make it behave even more sub-optimal....
I know you didn't ask for advice; but a simple thing: save a copy of your FMP plist file and you won't have to recreate the data viewer each time after a force-quit.
FileMaker usually hangs for me whenever I've got distantly-related unstored fields in the Data Viewer. Typical scenario: pop into Script Debugger during long script with multiple branches with Data Viewer open. Wait for every reference to resolve.
As I commented in the following Product Idea, I would love a Break key that would just stop EVERYTHING (gracefully, naturally)
sometimes the right thing is to connect to FMServer and kill the user, instead of force-quitting the application.
Agreed about the danger to local files. I waste a lot of time trying to find some safe way out, but there isn't usually one available.
And though I didn't solicit advice, I do appreciate the plist file backup method – that's a great idea. Thanks!