I am trying to search inside a pdf file. FileSeek shows that the query term is found, however, does not list associated line numbers. Attached is the view of the output. While my file contains multiple instances of the word 'the', FileSeek returns only a single row.

In trying to resolve this problem, I considered that maybe the particular file handler FileSeek is using to search within pdf files is the problem. My preferred pdf reader is NitroPDF, and my Windows 7 associates pdf files with that app instead of Adobe Reader. However, when I look at the file handles, I notice that FileSeek uses Adobe's file handler to search within pdfs. It appears as though there is no way to make sure FileSeek associates a different application with pdf files.

So, this approach didn't resolve the problem either. Am I expecting FileSeek to function in a way it wasn't intended to, expecting FileSeek to return all the instances of found query items instead of a single row when multiple instances of a query item was found?

I hope that all made sense!

Jon, if I understand you correctly, IFilters can let the calling program know if they found the sought text or not, but not *where* the IFilter found it. So, the problem lies with an IFilter, and not its implementation? That still leaves me wondering what the most robust solution to searching within PDFs is.

I agree - thanks Jon!