Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


I have Win7 x64 and installed Libre 3.4.3. All was well for a while. Then I
had the bright idea to install JRE 7 x64 and Base stopped working when
pointed at the path for JRE 7 (x64).

I uninstalled Libre, uninstalled all versions (x64 and x86) of JRE, and
reinstalled JRE (x86/32) 6 Update 26 and Libre x86.

Now Base won't run at all. When I check in another Libre application
(Writer), it won't accept the path

 c:\Program Files (x86)\Java\jre6  or any subfolder under here (bin or lib).

(It says "The folder you selected does not contain a Java runtime
environment..." WTF?)

I'm sure this is an old topic, but really, there should be some
documentation in the main site FAQ for Libre Office and Base and this JRE
nonsense.

Any suggestions would be greatly appreciated! Can't use Base, but really
don't wanna pay for Access or FileMaker...

thanks,
Clive

--
View this message in context: 
http://nabble.documentfoundation.org/Win7-x64-JRE-Base-tp3436648p3436648.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.