Paul Daunno Posted February 21, 2013 Share Posted February 21, 2013 I'm doing a Search All of [All Tools] [scripture] with the search argument of =Romans 8:11. The search does finally complete but I receive this error popup 3 times before it does. I've shut down all other Accordance workspaces, restarted Accordance and logged out of my Mac. I've attached a screen shot for reference. error.tiff Link to comment Share on other sites More sharing options...
Ken Simpson Posted February 21, 2013 Share Posted February 21, 2013 Hi Paul, thanks for this report. Can you please add a post with the version of Accordance you are using (from the Accordance menu - "About Accordance" and the version of the OS? (About This Mac under the Apple menu). That will help our tech guys in problem solving. Link to comment Share on other sites More sharing options...
Paul Daunno Posted February 22, 2013 Author Share Posted February 22, 2013 Ken, I'm running Accordance version 10.1.3 and OS X 10.8.2. Hope this helps in finding the root cause of the issue. Link to comment Share on other sites More sharing options...
Ken Simpson Posted February 22, 2013 Share Posted February 22, 2013 Just before we escalate this further, this crash doesn't happen on my system. Sometimes the search all cache becomes corrupt and needs to be rebuilt. To do this, go to Preferences (In the Accordance Menu) and the "Reading/Search all" tab. Towards the bottom there is a button that says "rebuild search all cache". Click this, press OK. Quit Accordance and restart (strictly this step should not be necessary). Then try your search again. It will take longer because it needs to rebuild the data, but let us know if it still crashes. BTW - why have you used = before your search? Seems redundant to me. What are you trying to search for exactly? Link to comment Share on other sites More sharing options...
Paul Daunno Posted March 3, 2013 Author Share Posted March 3, 2013 Ken, I followed your directions and still get the error. The reason I was using = before the search was because I assumed that would limit the results to only those hits for Romans 8:11. Is this not a correct assumption. By the way, if I do a search without the = sign I do not get this error. Link to comment Share on other sites More sharing options...
Sean R. Posted March 4, 2013 Share Posted March 4, 2013 You're correct, Paul. When the equals sign is not included [Romans 8:11], you'll also get hits where the desired verse is part of a range (i.e., Romans 8-9). With the equals sign [=Romans 8:11], Accordance limits the results to the specified verse. In other words, Accordance searches for that actual verse reference, ignoring ranges that include it. Link to comment Share on other sites More sharing options...
tebel Posted March 4, 2013 Share Posted March 4, 2013 I replicate this error on my system. I have the latest version of Accordance. Link to comment Share on other sites More sharing options...
Michael J. Bolesta Posted March 4, 2013 Share Posted March 4, 2013 I too get the same error if the equal sign is used before the Scripture reference. Link to comment Share on other sites More sharing options...
Ken Simpson Posted March 4, 2013 Share Posted March 4, 2013 Now that's interesting. =Rom 8:11 when it's used in the English field doesn't cause a mem exception for me, but when it's used as a Reference entry (as you would expect) then the exception occurs. (for me it occurs when searching the Comprehensive NT - not sure if it's the text or the notes, then Clarke's Comm, ACCS, Calvin, Halley's etc etc. I guess re the "why the =sign" is that it would seem that you are excluding a whole lot of potentially useful references. However, it certainly seems like it's a bug in the search all routine to me, but it doesn't cause a crash. Does it for you? Link to comment Share on other sites More sharing options...
Paul Daunno Posted March 4, 2013 Author Share Posted March 4, 2013 Ken, It doesn't crash Accordance it only pops up the message 3 or 4 times but then the search completes. BTW, I failed to mention from the onset that I was doing a Scripture search not Entry. As far as "why the =sign", I was just experimenting with some different search all options and wanted to see how the results differed. Even after a few years of using Accordance there are areas like Search All that still seem new to me Link to comment Share on other sites More sharing options...
Joel Brown Posted March 4, 2013 Share Posted March 4, 2013 I can confirm the error message during the equals search and will take a look! Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now