when the control "datasource as table" is open and
you are going to insert a new record - the button
"save" (the disk-button or other methods) will crash LO.
Since this is a database holding the data in memory,
all data inserted past the last "close" are lost
ODB-file does not get corrupt (says 7-zip etc, this is different/better than in former versions), which is not really remarkable, as that was the last working
.odb. however, the function "datasource to table" is essential for usability of Base and must be made "robust"
Don't know it works in 184.108.40.206, can not test ist, as that version will not be installed in here. - no samples available
On pc Debian x86-64 with 4.2.5 LO Debian package, I don't reproduce this.
Perhaps Windows only bug?
When you say, 4.2.5 "will not be installed", do you mean you've got a technical problem to install it or you're not authorized to install it?
supposed the sourceastable-view is open and you enter a new record (empty form by using the yellow star or copying by "dragndrop"):
in principal base has two options to committ update/storage:
-- use one of the "save"-buttons
-- change the the record-line in any grid-control
Version a) producess frequently (not always but .. ) a LO-crash
version b) when using the mouse and click in any grid (sourceastable or gridcontrol) to any line of an existing record, LO saves the recent record and changes the pointer - as expected
For your guidance:
The function "sourceastable" is quite new, and it behaved buggy as stated above in any former versions, however, it is needed, and it would be great if that view-control and the personal forms could co-exist safely, but it ooks as the have effects to eachother
I regret, that there will be no further infos - the database ist gone with the crash and there will be only screenshots from the recovering-window.
I am the admin in here, and at actual reading the issues I do not treat 4.2.5 as stable enough.
probably this is a doublicate to issue 79786 ,
so may be I should wait for the coming 4.2.6
Indeed it may be, so let's put this as dup.
Don't hesitate to reopen this tracker if you still reproduce this with 4.2.6
*** This bug has been marked as a duplicate of bug 79786 ***