Hi Steve,

I believe one reason for this was that a smart finder file did not have the complete pair of the index and random files, either for the standard smart finder search, or the special files used when smart finder has one or more criteria.

Softrak Support's previous reply on this thread, on May 8, referenced some file pairs OEF###'I / OEF###'R and OEMFCT'I / OEMFCT'R. The first pair is for remembered smart finder search results (which are supposed to be deleted when the user associated with the SF search closes the program), and the second pair is the multiple-criteria smart finder.

The solution would be to ensure that no-one is in the data, then remove the unmatched file.