The ability to abort a search if you see you've made a mistake and you have a big file is a good idea, and I think a progress tone to say the BP is still searching is also worth considering. ----- Original Message ----- From: "ptorpey" <ptorpey@xxxxxxxxxxxxxxxx> To: <bookport@xxxxxxxxxxxxx> Sent: Tuesday, February 22, 2005 1:24 PM Subject: [bookport] Searches in Large Files Every once in a while, I perform a search for a text string in a large file. If the text is not in the file, or at the end of a large file, the BP will, of course, not respond for many seconds. The first time or two this happened, I thought that the BP had locked up. Now, if this happens I know to wait. However, the user may not always know where a certain text string occurs in a file (after all, what is a search for?). Thus, if the search string is far from the current position in the file, the searches will naturally take a long time. I wonder if there is any way of escaping from such a search so that the user can get on with his/her work or move more quickly through the file. Is it worth thinking about adding such an escape key/function to the BP? What do folks think - Have others experienced this? -- Pete