Description: LibreOffice 7.1.0.3 on Windows 10 Build 18363 HSQLDB Embedded with Java JRE 1.8.0_271 AND AdoptOpenJDK 11.0.10+9 HotSpot fail with Villeroy's FilterData.odb from https://forum.openoffice.org/en/forum/download/file.php?id=40136&sid=e9f3a31fe7e049a77a0fe3d55abd07af Note: other DB's work. Ratslinger downloaded the same file and it worked for him. Steps to Reproduce: 1. Open the FilterData.odb 2. Click on any Form presented. 3. Actual Results: General error: org.hsqldb.lib.FileSystemRuntimeException: java.io.IOException The connection to the data source "FilterData" could not be established. Expected Results: Open the form. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: https://ask.libreoffice.org/en/question/294969/how-to-connection-to-base-to-embedded/ 1) I uninstalled Oracal Java, downloaded and installed AdoptOpenJDK 11.0.10+9 HotSpot 2) I installed AdoptOpenJDK 11.0.10+9 HotSpot (the default) and made sure that it is selected ( Menu Tools->Options ->Advanced (dot in the circle left of Java version) and 'Use Java runtime environment' is checked.). 3) Still fails - same error. 4) I deleted FilterData.odb, downloaded it again, have the same error.
Created attachment 170008 [details] Showing current JDK
No repro Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded using: java-11-openjdk-11.0.10.0 (from openSUSE 15.2 distro packages)
No repro Version: 7.1.0.3 (x64) / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 1; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded using AdoptOpenJDK 11.0.9.101-hotspot
I completely deleted LibreOffice from my machine, downloaded, and re-installed it again. Now, the file in question did open! I deduce that old files from 8/20/2015 remained after the many updates and may have contributed to this failure. The true bug may be in the cleanup routines of updates. Thank you.