This bug was filed from the crash reporting server and is br-5540705e-3d71-4c08-bdb8-4e1ea64eac49. ========================================= Connecting to existing firebird3.0 file via "existing Database" (not ODBC,not JDBC, not embeded) Version 1: add new data into not-empty datase. As long as you stay within LOBASE all looks nice. Leaving LOBASE and reentering... new data is gone to data-never-nerver-land. No red "save" Arrow Synmbol gets visible. (all entries and changes via FLAMEROBIN are o.k. and visible in LOBASE.) Version 2: Using empty newly created Database trying to add new fields via design-view you can enter field names and key and then ... !!!! big crash don't get so far to enter table-name.
Please don't report 2 bugs in one report. Open a new for "version 2: ...". I have tested the input of data to an external Firebird file. I have written data into a table. Changing the row seems to save the data. You could add more rows - all seems to be OK. The button for saving data doesn't show there are data to save, but I have pressed it. Closed the database, reopened it an the data have been gone. Then I have written the data in the table again and created also a new table. The button for saving data is activated, so I could save the data. Closed the database, reopened it and the data will all be there. Bug appears in LO 6.1.4.2 on OpenSUSE 15 64bit rpm Linux. I will change the title of this report to this special problem.
Created attachment 148671 [details] Database and Firebird-file. You have to change Edit > Database > Properties > URL The attached *.zip folder contains a database, connected to a Firebird-file. You have to open the *.odb-file and change Edit > Database > Proberties > URL to the *.fdb-file in your system. You could also set the URL to a not-existing *.fdb-file. Base will create a new file then. Input of data seems to work, but data will be lost, because saving isn't activated.
Have seen this bug is already reported: bug106463. So I set this one as a duplicate. *** This bug has been marked as a duplicate of bug 106463 ***