you're right; I was wrong.
These updates are quite necessary if one is on-line with the program.
From: V Stuart Foote <VStuart.Foote@utsa.edu>
Date: Mon, Aug 3, 2015 at 7:18 PM
Subject: [libreoffice-users] Re: probllem about microsoft visual c
If LO 3.4 is still available, then I would suggest you download that
it works error-free.
As do virtually all "releases" of LibreOffice. And, if you must "revert"
the archival builds for the project releases are here:
Not trying to be harsh here, but, even the last 18.104.22.168 release from that
series is rather outdated. Frankly even an OpenOffice 4.1 release would be
more appropriate than advising folks to use the LibreOffice 3.4 release
builds. Please stop continuing to suggest them as viable for users.
Regards OPs issue with Visual C runtimes, as long as the x86 MS Visual
Studio C++2010 versions (msvcr100.dll)
installed for the 4.3 or 4.4 releases--the 22.214.171.124 should provide good
But if moving to a 4.4 install (via upgrade, or clean install) it would be
wise to clear your user profile. That has resolved similar C++ runtime
issues for folks.
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
- Re: [libreoffice-users] Re: probllem about microsoft visual c · anne-ology
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy