16 replies to this topic

[BarryF]

How many different macros are there?  Is it possible that the macros were not all installed correctly?  Is there a way to verify this?

[BH.]

It does not matter which version of the macros you have installed, only that one is installed.

[BarryF]

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.

[BH.]

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.

[BarryF]

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?

[Paul Coetzee]

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=*

[BarryF]

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.