Smart tag (getting Bible ref inserted) stopped working after upgrading to ver 6
I ordered a free set of books. To install I needed to get the free ver 6 engine. After doing this when I have a Bible ref in a Word doc I can no longer right click and have the replace with text option. Does anyone have a suggestion? I've tried the Tools--Options--Proofing--Auto.... thing but that does not help. I do notice the available actions has "Logos Bible Software 5." I wonder if that is throwing it off. If so I still don't know how to fix it.
I can roll it back with Macrium6 but would rather keep ver 6 if possible.
Thanks!
Comments
-
See this thread. There are several different suggestions spread through this thread, including a PowerShell script provided by logos. You should be able to get them working with one of those solutions. I would try the PowerShell script first.
0 -
Thanks for the reply, but I see no thread indicated in your response. Maybe I'm missing something.0
-
The part of the thread with the Powershell 'fix' is https://community.logos.com/forums/p/105737/735038.aspx#735038 but you should read other posts, particularly if you installed 64-bit Office. But if you are using Office 2016 you will have to wait for Faithlife to fix Smart Tags.
Dave
===Windows 11 & Android 13
0 -
Currently I'm using Win 10 and Office 2010. Thanks for the link to computer programing 101! I may give that at try when I have time to kill. Until then I hope Logos comes up with a fix so their software will cooperate nicely. For now I'll roll back to 5 which was working fine. Thank you again for your time and the necessary information. It's very much appreciated. We are all busy and have other things to do!
This morning when I start Logos it wants to update first, which was the cause of may problems. Other than clicking the "No" button every time, is there a way to turn the updates off?
Thanks!0 -
Donnie Gullion said:
I may give that at try when I have time to kill. Until then I hope Logos comes up with a fix so their software will cooperate nicely.
The Powershell post is the fix! The issue arises when upgrading from Logos 5 (32-bit) to Logos 6 (64-bit) but also arose in Logos 6.3 when Faithlife introduced a different method to update the application.
Donnie Gullion said:This morning when I start Logos it wants to update first, which was the cause of may problems. Other than clicking the "No" button every time, is there a way to turn the updates off?
You can delay updates by setting Automatically Download Updates to NO, but there is no way to prevent that without going offline.
Dave
===Windows 11 & Android 13
0
