How many different macros are there? Is it possible that the macros were not all installed correctly? Is there a way to verify this?
Can't get Bible Search Tool to find first Bible
#11
Posted 19 March 2014 - 01:21 PM
#12
Posted 19 March 2014 - 01:22 PM
It does not matter which version of the macros you have installed, only that one is installed.
#13
Posted 19 March 2014 - 01:24 PM
I have attempted to index CEV, ESV, NLT, GNB, BBE, AMP, and KVJ. All of these are installed and work fine in my e-Sword program.
#14
Posted 19 March 2014 - 01:28 PM
Regarding the files under my documents\BibleSearchTool\Bibles directory there is only one file and it has .bst as the name (nothing before the dot). This is the only file. Since there are no names of the versions that I attempted to index, I would guess that this is not what I would hope to see.You should see one BST file per version. GNB.BST. Since you do not have these, then the indexing process did not work. Why is not clear to me.
#15
Posted 19 March 2014 - 01:57 PM
If I delete the existing .bst file within the Bibles menu, I can verify that it is no longer in my directory. But it is rewritten there as soon as the indexing of my first version is completed. That seems to me to say that something in the indexing process completed abnormally therefore it did not build the file that it intended to be written as KJV.bst for instance. I don't suppose there are any logs created by the process, are there?
#16
Posted 19 March 2014 - 04:39 PM
The other thing that I might have done is change Bibles=* to Bibles is KJV en then rebuild the KJV
To change settings of bibles=* double click on it and a new window open where you can change it.
After that change it to Bibles=*
#17
Posted 20 March 2014 - 10:10 AM
Brent help to solve this problem, but we are not exactly sure why.
After he had me test various functions in the hotkeys program, the Bibles would index properly and subsequently showed up in the Bible Select window. The time it took to run an indexing of a particular version increased by 2 or 3 times to between 9 and 19 seconds each. So this to me meant that something was not being executed in the original attempts to index the versions when it failed.
The only thing that I can guess (and it is just a guess) is that some variable was not initialized properly until we used the hotkeys.
The end result is that everything works now.
Thanks for your help, Brent.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Similar Topics
My installed Bible files do not show up in my e-Sword folderStarted by Guest_Bim Kadosh_* , 04 Apr 2024 |
e-Sword ToolTip Tool NTStarted by Guest_BH._* , 02 Jan 2012 |
Download from Bible Support to e-SwordStarted by Guest_Alanorei_* , 27 Mar 2024 |
Formatting New Bible translation for use in eswordStarted by Guest_DocStu_* , 20 Mar 2024 |
Linux Mint 20: E-Sword 12 search not linking to verse resultsStarted by Guest_songdove_* , 15 Mar 2024 |
Frequently Asked Questions
Latest Blogs
- 10 justifications for Bible reading
by SarahSherrill, Jun 27 2022 02:53 AM
According to the experts from Astros DigitalHere are ten reaso... - How can I fix the Cash App if it isn't Working?
by cashcardhelps, Jun 07 2022 01:12 AM
First, you must keep the app up to date with the most recent v... - How can an app benefit your pharmacy in growing business earnings
by Alteza, Jun 06 2022 03:14 AM
Apps comprise a large portion of the tech-driven society that... - What Is a Satire Essay Anyway?
by Caleb9, Jun 04 2022 08:22 AM
What Is a Satire Essay Anyway?A large number of professional w... - 25% OFF on Mauli Thread Rakhi Online for Brother
by giftsvalla, Jun 03 2022 02:02 AM
Mauli Rakhi are generally red. The red colour symbolizes stren...