Exporting a Bibliography to Excel isn't working on 5.3 (either a new or open document). You get the little progress indicators, but nothing happens. Exporting to Word, or saving as a CSV is fine.
This is on Windows 8.1 64-bit, Office 2013 32-bit.
I'm not seeing an Export to Excel option (and don't know how to get one...)
Then I am clearly special [;)] (or I was doing it from the Collections tool and forgot to mention that [:$]). It's broken from Library too, now that I've checked. It would be nice to have some consistency between these three locations.
It's broken from Library too
I guess that's what you get for trying to use prototype features that haven't been announced in the release notes yet? [:P]
This feature's not ready for use yet... stay tuned.
I guess that's what you get for trying to use prototype features that haven't been announced in the release notes yet?
That's what YOU get for adding features without telling us. [:P][:P][;)]
It works from Collections & Library here, same setup. But it's painfully slow. Maybe because Excel is activated before writing to it for testing purposes? Clipboard, XML, temp csv file would seem faster.
Exporting to Excel is provided as a convenience. It's likely to be very slow for a large collection (because each cell has to be sent to Excel one at a time).
You should use CSV export if you want to create an Excel file. (Note that Excel will corrupt Unicode data in CSV files, but Google Docs can import it OK.)
I am trying to export to Word re: Collection --> My Logos Library (large) --> Print/Export --> then the wheel goes on and on and on and Logos Crashes! Is anyone experiencing similar problem?
Thanks!
I am trying to export to Word re: Collection --> My Logos Library (large) --> Print/Export --> then the wheel goes on and on and on and Logos Crashes! Is anyone experiencing similar problem? Thanks!
It would be best to create a new thread and explain your issue clearly, providing appropriate details (i.e. what version of Logos? What OS? What steps? etc.)
In addition to what Alabama suggests, can you posts whether you're running 32 or 64 bit version of logos. Logs would also be helpful: https://wiki.logos.com/Diagnostic_Logging
I can't reproduce on Windows with 64 bit Logos, but I do note that it uses more memory that I've seen Logos use, above 1.5GB total.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
