As you can see, information in important in determining what the problem may be. The more information you can provide on what is going on like upgrading from another LO version; 32 to 64 bit; DB change the more likely someone can help. Without the info, it is best guess. Thank you for your help. Glad all is working. Probably incorrect bit version from previous set up.
Just need to select one in Base. I have 4 or so installed. As you have been helped, please help others to know the question has been answered by clicking on the in upper left area of answer which satisfied the question. You can also close the question by clicking on the X close lower right corner of your question. I changed nothing in this regard. Fun stuff. It comes and goes based on mood swings I guess.
All these because of either upgrades in version or because of testing for others. It has not come and gone or been finicky. I can install to system folders where it is found automatically or place it in a user folder where when pointed to it remains.
Hrbrgr helped me by showing me it was related to a corrupt user profile. Once I reset that in safe mode, normal functionality was restored, and Java became visible again. If MySQL is installed locally, no problem. Java not showing up was simply one of the many sour symptoms. Had same problem with earlier versions - 5.
The type of data base??? I am not a power user and just created the data base s with the databases residing on my PC. None of them work.
They have worked fine for several years with earlier versions of LO. I am currently using 1. I am using embedded DB No changes to LO that I am aware of I can create a new file but when i click on tables thats when i get the error I will update java and report the result. Just moved over to my Debian system. Have LO v5. Debian comes with Java 1. Just tested with the 1.
The only difference at this point may be the LO version. You never mentioned if you are using the distro version. I got that error message on Base installing it for the first time on pop os. I got it fixed installing the following:.
0コメント