Logos Library Reporter
Comments
-
Dave Hooton said:
BTW I updated to LLS 1.0.4 OK.
Thanks Dave for letting us know that LLR 1.0.4.0 loaded and is working!
Dave Hooton said:I don't use IE but this morning it told me "Your browser has been upgraded". Fearing the worst I checked the version, but it still showed IE9 2011;
i have been in this same situation before and seen this message, like you i was relieved to see IE still at version 9
Dave Hooton said:which I like for use with Libronix.
ditto
Edit: what started the IE9 thing was when i spent some time updating the Reports Tab on LLR's website.
0 -
Hi Steve
I've only just got round to installing your program.
It installed fine and works well - this is on Windows 8.1
Great job - really appreciated[Y]
Graham
0 -
Hi Graham,
Graham Criddle said:It installed fine and works well - this is on Windows 8.1
Thank you Sir for letting us know that it worked for you!
i'm glad you are finding LLR useful!
0 -
Happy to say it worked for me with the production version of Logos.
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
hi abondservant,
abondservant said:Happy to say it worked for me with the production version of Logos.
Thank you Sir for letting us know that LLR installed and is working!
0 -
New Update to LLR is available (ver 1.0.5.0)
This update has 1 new Report and 7 improvements and 2 fixes. See the release notes to view these changes.
New Feature, reads exported XMLs from Logos 5.3 Beta2! (read more in the above release notes and in the announcement in the Beta forum)
Added report Catalog Summary which shows you interesting details on a Single Catalog.For those who want to install this new Update, please go to the Download page on the website and follow the instructions.
[users who already have LLR installed, please follow Step 1 carefully]Edit: if you find a problem with LLR, please email me: admin [AT] clark-tx [DOT] net
Also please attach the LogFile (Documents\Logos Lib Webpage\LogosLibReporter_Logfile.txt) to your email.0 -
I haven't been able to get this to work with the xml file from 5.3 Beta 2 (running LLR in a vm on my Mac). I'll email you the logs
0 -
Hi Jon,
Thanks for emailing me the logfile.
As I replied via email, my guess is that you don't have L5.3 Beta installed in your Mac VM, but have it installed only in the Mac. So LLR doesn't find the necessary info for L5.3 Beta in your VM for Mac. LLR was initially designed to run where L5 (or L4) was installed.
This is a unique case in which i did not anticipate (but i can see how it would be useful for Mac users). So i am working on allowing the XML feature in LLR to work even when L5.3 Beta is not installed. It will warn you tho when you have Read Logos Catalog DB selected and press the Read DB button (the warning will tell you that LLR could not find L5 running in your user account). But it will work when you select Read Exported XML File and press the Read XML button (when i get it fixed).
As i said, your case is unique. All those who run L5 in the same user account as LLR is installed should have no problem (this should include most users).
Thanks Jon, i will get back to you via email when i get it working.
0 -
We got Jon's problem solved. This will be included on the next release of LLR.
It will allow those who use a Mac VM to install and run LLR. But you will need to save your XML files from your Mac install into a location where the VM and LLR can find them (edit: if you don't have L5.3 Beta installed in the VM, otherwise you could run L5.3 Beta in the VM and export your XMLs there.).
Edit: Thanks Jon for all your help!!
0 -
[Y]
0 -
New Update to LLR is available (ver 1.1.0.0)
This version has 1 Fix, 2 Updates, and 15 New Features.
See the release notes to view these changes. (illustrations included)Summary of changes
- Update: LLR works with Logos/Verbum 6.1 Beta
- Fix: LLR Scales to your Window's Scaling
- New: Support for Verbum users
- New: Support for Multiple users
- New: Support for Mac users running Windows in a Virtual Machine (without Logos being installed in that VM)
- New: Web Installer
- New: Comments next to Save DB and Backup DB buttons
- New: Settings tab
- New: Setting to assign OWNER values for User Folders
- New: Setting to pre-populate AKA box or NOTE box
- New: Info saved with Backups
- New: Add/Edit button for altering Backup info
- New: Display Backup info for selected items
- New: Refresh button for the Backup Listbox
- New: Copy from Backup moves backup info into LLR's working folder
- New: LLR icon
- New: More info on the 'Currently read DB' area
- Update: Scrolling in the Reports selection area
For those who want to install this new Update, please go to the Download page on the website and follow the instructions.
[users who already have LLR installed, please pay attention to the ALERT]if you find a problem with LLR, please email me: admin [AT] clark-tx [DOT] net
Also please attach the LogFile (Documents\Logos Lib Webpage\LogosLibReporter_Logfile.txt) to your email.Edit: just found a bug in LLR's download webpage for Chrome users. I fixed this bug, when you go to LLR's webpage, tell your browser to Refresh and the download portion of the webpage should display properly. Sorry that i missed this.
0 -
Any way you could make it include ISBN numbers in the reports?
ALSO its working well in the latest beta, on win 8.1L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
abondservant said:
Any way you could make it include ISBN numbers in the reports?
The ISBN information is Not in the catalog info from Logos. So no, LLR cannot display something that is not there. Sorry [:(]
Edit: Thanks abondservant for letting us know that LLR is working with the new L6 beta!
0 -
Problem with LLR
i am working with Tes in Europe who's computer is setup for 24-hour display. This is causing some problems with LLR. LLR's code is building date/time strings and when those computers are set for 24-hour, they force LLR's code not to display AM/PM info for the time.
i am working on it and will post a fix for LLR when i get it resolved and fixed.
0 -
New Update to LLR is available (ver 1.1.0.2)
This version has 2 Fixes.
See the release notes to view these changes.Summary of changes
- Fixed crashing for the Edit Catalog operation. This was due to LLR not handling computers which have 24-hour time as their standard.
- Fixed crashing during the LastUpdated Change Report. This would effect European users who use the Date format with decimal points used as separators.
The first time that LLR is run after this install, it will adjust date/time to use the AM/PM in LLR operations. You will see this in the Saved Catalog DB listbox and the Backup listbox. Also when you click on any item in the Backup listbox, the new info file will be updated.
Please apply this update to your LLR install.
For those who want to install this new Update, please go to the Download page on the website and follow the instructions.
[users who already have LLR installed, please pay attention to the ALERT]if you find a problem with LLR, please email me: admin [AT] clark-tx [DOT] net
Also please attach the LogFile (Documents\Logos Lib Webpage\LogosLibReporter_Logfile.txt) to your email.P.S. Thanks Tes for allowing me to use your computer for hours while i tested these fixes!
P.S. (2) Users who had installed LLR ver 1.1.0.0 will not need to uninstall LLR prior to installing this update.
You just need to close LLR and then reopen LLR, you should see a notice (see image below) asking if you want to install the newer version (click OK to allow LLR to be updated).
0 - Fixed crashing for the Edit Catalog operation. This was due to LLR not handling computers which have 24-hour time as their standard.
-
[quote user="steve clark"]i am working with Tes
[/quote]
"I am working with Tes" Our dearest brother Steve is too generous to mention me as if I associated him in his diligent work in fixing the LLR which took him 61/2 hrs. The opportunity was he contacted me by teamviwer to help me as usual, he has done for years, which I am so grateful for his commitment to help for those of us who are less privileged in technical knowledge. While he was updating the LLR for me, he noticed that there was a bug in the program. I waited some hours watching him and went to bed. I slept well and he continued to fix it until he finally got the job done. He did it on my computer. I cannot even consider it as a slight contribution. It is not to mention at all comparable to his hard work. It is me that who has benefited from his wonderful work. May the Lord bless you my brother. I would like to thank you on behalf of all of us who are in Europe to fix it for us.
.
May The Lord bless you my brother Steve.
Blessings in Christ.
0 -
0
-
Thank you Steve.I am really excited. It is wonderful to see and arrange my resources through the multiple functions you have provided. May the Lord bless you abundantly more and more.
Blessings in Christ.
0 -
-
I was just about to ask if anyone knew of an easy way to compile a list of one's Logos library, and then I saw this. This is awesome! Thank you, Steve!
0 -
-
Coming Soon:
Speed improvements for those with large libraries. It is currently in beta and i hope to release it in the near future.
Restructured the SaveDB writing routine to the LLR db. This speeds up writing catalog info to LLR's db.
Tested with catalog containing 5000 books
Previous time to add was 10.5 minutes
New time to add is now 6.4 secondsFound that on large catalogs the All by Type report took very long to build.
Tested with catalog containing 5000 books
Prev time to build was 5 minutes
New time to build is 10 secondsFound that the All by Tags report took a long time also.
Tested with catalog containing 5000 books
Prev time to build was 3.6 minutes
New time to build is 24 seconds0 -
Sweet! [:)]
0 -
New Update to LLR is available (ver 1.2.0.0)
See the release notes to view these changes. (illustrations included)Summary of changes
- Improvement:Increased Save DB write speed
- Improvement: Increased speed of the All by Type report
- Improvement: Increased speed of the All by Tags report
- Improvement: Added word wrapping for Titles and Extra Info fields in the reports
- New: Added Subjects changed report
- New: Added Abbrev. Titles changed report
- New: Added Hidden Book Differences report
- New: Added a new Setting: Show User Titles
- Improvement: Made improvements to printed reports
- Improvement: Cleaned up the Added or Missing Books report
- New: Added a new button for recovering a corrupt LLR database
- Misc. Changes
For those who want to install this new Update, please go to the Download page on the website and follow the instructions.
[users who already have LLR installed, please pay attention to the ALERT]if you find a problem with LLR, please email me: admin [AT] clark-tx [DOT] net
Also please attach the LogFile (Documents\Logos Lib Webpage\LogosLibReporter_Logfile.txt) to your email.Thank You Dave for your time, help and suggestions during the beta!!
0 -
Thanks Steve!
0 -
Yes, thank you, Steve! [:)]
0 -
[Y]
0 -
-
LLR is working incredibly fast for me, Steve. The only problem is that I just replaced my HDD with an SSD, which has accelerated all my apps, so I can't really tell how much of the new speed is due to what.
0 -
-
i have updated the LLR User Manual on the website.
Edit: for feedback on LLR add your posts to this forum thread.
Edit2: the website is up-to-date, the Reports tab is finally done.
0 -
New Update: 1.2.1.0 See details in this L6 forum post
0 -
[Y]
0 -
Blessings in Christ.
0 -
Running LLR on Windows 10
0 -
[Y]
0 -
Dear sir,
First of all, I want to thank you very much for your program. It is simply excellent! :-)
I'm sorry to bother you and I do not know if you'll have time to answer me.
However, I am sending you a copy of an error message.
Everything worked well for a long time and suddenly the problem happened.
I have uninstalled your program several times but this does not solve the problem. I have reinstalled "vcredist_x86 Microsoft" too (I am working whith Windows 10 and I read your post about it).
My library is about 40GB heavy.
Can you advise me something?
Thanks in advance.
Sincerely,
Franck
0 -
Hi Franck
I'm sorry to have to advise you that Steve Clark - who produced this application - passed away two years ago.
His son let us know at https://community.logos.com/forums/t/127178.aspx?PageIndex=1
Graham
0 -
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.
0 -
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 11 & Android 13
0 -
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,
0 -
Dave Hooton said:
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
===Windows 11 & Android 13
0 -
Dave Hooton said:
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.
Have joy in the Lord!
0 -
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,
0 -
Franck said:
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.
Franck,
Great to hear it helps you a bit,
Mick
Have joy in the Lord!
0 -
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.
- Anyone having the same problem, or is it just me?
- Might anyone out there still have a Library XML file from 7 to compare vs 8, to see if the format has changed? If the XML format has changed between 7 and 8, I wonder if 8's format could be easily edited so that LLR would accept it.
Thanks,
-Pete0 -
Pete De Bonte said:
Anybody have LLR working with 8?
yes. I just now read the exported library xml from Logos 8.12 into LLR, worked fine.
Have joy in the Lord!
0 -
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*
-Pete0 -
Pete De Bonte said:
Thanks NB Mick! Your success encouraged me to retry it
Good to hear it's working now for you!
Have joy in the Lord!
0
