Hi Graham,
I am so sorry. Thank you for letting me know.
I am one of the lucky beneficiaries of Steve Clark's work.
Thank you Graham.
It is inevitable that Faithlife will change database schema, and LLR will be incompatible. The current version is 2.5 years old and I doubt that it can be fixed, even though the web site is still running. However, I sent an email to its Admin address, so I'll see what eventuates.
Dave===
Windows 10 & Android 8
Hello Dave,
I already sent two emails to the Admin address but I did not get an answer. That's why I posted my question here.
But, given Steve's departure, I prefer not to go further and not insist, by delicacy towards his family.
I thank you Dave for your understanding and for your answer.
Regards,
Dave Hooton:I sent an email to its Admin address, so I'll see what eventuates.
The reply from Josh Clark stated "...After my Dad’s passing in 2016, the code was frozen. I am saddened to hear that it no longer works."
Dave Hooton: Dave Hooton:I sent an email to its Admin address, so I'll see what eventuates. The reply from Josh Clark stated "...After my Dad’s passing in 2016, the code was frozen. I am saddened to hear that it no longer works."
Dave & all,
just to verify (I think I used LLR a looooong time ago, and I think on another machine), I installed the exact C++ runtime version needed for Win10 you linked to in your post on the other thread and installed LLR from the website. Installation went fine.
Trying to read the Logos library directly from the DB did not work (Logos 7.17 Beta 3) and gave an error message much like Franck's above. However, using the second option Steve built into LLR, namely exporting the library as an XML and reading that file worked without a problem. I had it produce some reports, no issue (except that it will find zero hidden books using this method, since they are not shown in the library and thus are not part of the XML export)
So it seems, the tool still works for the time being:
The XML file needed for this can be easily build - it is called library.XML and LLR will import it and work - at least on my machine.
Running Logos 9 latest (beta) version on Win 10
Hi NB Mick,
I thank you for taking part in the conversation. Your solution works well but I do not have access to book covers and this is my big need. Indeed, the software explains to the tab "Book Covers": "Book Cover report can only be built from a Catalog.db, not XMLs".
But let's stay there. This will force me to focus more on the subtleties of the library option in the Logos 7 software itself.
Best regards,
Franck: thank you for taking part in the conversation. Your solution works well but I do not have access to book covers and this is my big need. Indeed, the software explains to the tab "Book Covers": "Book Cover report can only be built from a Catalog.db, not XMLs". But let's stay there. This will force me to focus more on the subtleties of the library option in the Logos 7 software itself.
thank you for taking part in the conversation. Your solution works well but I do not have access to book covers and this is my big need. Indeed, the software explains to the tab "Book Covers": "Book Cover report can only be built from a Catalog.db, not XMLs".
Franck,
Great to hear it helps you a bit,
Mick
Anybody have LLR working with 8? I tried to read a Library XML file exported from Verbum 8.12 today, and LLR said:
Error: could not find an expected RootName in the XML file.
Thanks,-Pete
Pete De Bonte:Anybody have LLR working with 8?
yes. I just now read the exported library xml from Logos 8.12 into LLR, worked fine.
Thanks NB Mick! Your success encouraged me to retry it, and I've discovered that "Error: could not find an expected RootName in the XML file." occurs if I (accidentally) export as "Spreadsheet (Excel, etc.)" rather than XML.
It's confusing, because the two options are close together (can easily miss and click the wrong one), and moreover, the filename is still "Library.xml" even for the "Spreadsheet (Excel, etc.)" option, which is probably why I didn't realize I'd clicked the wrong option.
Maybe Faithlife should change it to have more distinctive filenames. *shrug*-Pete
Pete De Bonte:Thanks NB Mick! Your success encouraged me to retry it
Good to hear it's working now for you!