-Problem doing a morph search in the NKJV

Bummer, I thought we were going to really get somewhere with this.

Well it wasn't that bad, we did discover that apparently 'Bradley' and 'fgh' are the same person - one posing as another-?.

But I would still consider it a noteworthy move on the part of Bradley[fgh] to answer the question posed; silence is not very becoming of a Logos Rep.........

Richard DeRuiter said:

Room4more said:

AND they are the same bible dataset that's been cloned to make three resources to sell to us?

No.

Each morph search is done on the reverse interlinear of the Bible being searched. When that Bible is out of sync with its own reverse interlinear the morph search fails. The bug referred to above is a known issue that prevents the preferred Bible from updating, even when its reverse interlinears do. Hence the problem searching.

This has been noted in the NASB, NRSV and now the NKJV. When version 5 was in beta testing, I had the same issue with the NIV.

They aren't the same data set cloned three times. Each reverse interlinear is created for each Bible (because some make slightly different textual choices for their base text). The Bible index created for each reverse interlinear Bible is unique to that Bible. That's why a search might work in one version, but not another. It's also why the morph search fails, even though the new interlinear is present - that Bible database for that Bible has data that doesn't work, because of the mismatch.

Does this make sense yet?

okay lets speculate for a moment and say that this writ is true.

You are pre-supposing that this inherent flaw is thus carried over from L4 to L5, since this is the current location of the thread and dealing w/the most current release that should go thru the resources and update as well as upgrade the program and/or resources.

Which inturn can be a flaw located within the auto-update, most affected are those that have "prioritized resources". For myself, I do not have "prioritized resources" so i didn't fall victom to this and in turn have never experinced any problems with any and/or either of the resources in question.

Which still does not clear Bradley, since the question was posed to him - yet another speaks and really does not and cannot say undoubtedly that they are 100% correct. Which also is not an un-common thing within the forums, and speculation runs deep....[ i just love how we speculate, doesn't it just give you goosebumps and make you tingle all over....]

eh, Bradley?

But many like this way and will be happy......so I guess[speculatively]:

be happy.

dinners ready. i may return to read some more - speculatively of course.....

Richard DeRuiter said:

Room4more said:

yet another speaks and really does not and cannot say undoubtedly that they are 100% correct.

If you're referring to me as the 'yet another,' let me say that I'm 100% sure that I'm 100% correct. I'm not guessing, speculating, theorizing, or making it up as I go.

This is a known bug. We know what it is. We know what causes it. We know how to identify it. We know how to fix it.

I had something else wrote but decided it was frivilous, we know that there is a suspected bug, so lets keep it simple:

Do you write any of the three data set(s) in question?

Richard DeRuiter said:

Room4more said:

I had something else wrote but decided it was frivilous, we know that there is a suspected bug, so lets keep it simple:

Do you write any of the three data set(s) in question?

It's obvious you won't accept an answer from anyone who isn't a Logos programer, so I'll stop writing now. 

So in other words - No.

I didn't think so. Blows away your

If you're referring to me as the 'yet another,' let me say that I'm 100% sure that I'm 100% correct. I'm not guessing, speculating, theorizing, or making it up as I go.

100% accuracy doesn't it? Of course you can still answer and dispell any speculation...

[besides the question was posed to an actual Logos Rep. - wasn't it?]

But I do appreciate your honest attempt to speak in his stead; seems to be happening alot lately. Appears we are having another:

or are we just really haveing a communication gap? I say NKJV and you say NRSV/NASB - NIV added

Bradley Grainger (Logos) said:

Hi.

It's hard to read tone on the forums, so I'm not sure if you were being serious when you wrote that fgh and I might be the same person, but I can tell you that we're not. (But then I would say that, wouldn't I? That's a joke BTW. We're not the same person.)

There is a known bug in Logos 4.6a that can cause a Bible to not update properly. The consequence of this bug is that it can cause morph searches to fail (as well as other reverse-interlinear-related features such as Speaker labels or inline reverse interlinear display). It can happen to any reverse interlinear Bible, but should usually just happen to one specific Bible for each affected customer. I can provide more details about the bug if desired.

This bug is already fixed in Logos 5, and will be fixed for Logos 4 users when 4.6b ships. Until then, a workaround is to change Bible prioritization and then run "update resources". 

Interesting, I have been up to date reading about the issue but never had the pleasure of experiencing the issue, i do find it concerning that it seemed to infect a single user w/multiple bibles. would not the auto-update caught this?

edit: but the user seems to be running L5--?

Bradley Grainger (Logos) said:

Room4more said:

edit: but the user seems to be running L5--?

Even though the bug is fixed in Logos 5, he could still be affected depending on when he last updated resources in Logos 4.6x and when he upgraded/updated to Logos 5.

If he is running Logos 5 (which he may be, since the problem was first reported on the "Logos 5" forum), then the fix is just to run "update resources". (He won't have to bother with re-prioritising resources; that's just for Logos 4.6a.) 

http://community.logos.com/forums/t/66058.aspx

Bradley apparently the auto-updater is not working correctly, why should we have to run a command when thats the job of the autoupdater? notice and correct.....

Bradley Grainger (Logos) said:

Room4more said:

Bradley apparently the auto-updater is not working correctly, why should we have to run a command when thats the job of the autoupdater? notice and correct.....

The bug leaves the program in a state where the auto-updater doesn't automatically download the updated resources (even though the bug that initially caused that problem is fixed). Running "update resources" (which is needed just this once) will clear up the problem. After that, the auto-updater will work properly.

sounds more like a virus than a bug, so then why not write a script to update the autoupdate that does the restart command, when the program restarts it should re-run the autoupdater which in turn should sqeulch the virus bug, it could run thru the sync mode...phones ringing......