We have verified this bug exists on Windows installs of 3.2.2 and 3.4.0 Final (2011-06-03).
Open a database in the Base app.
Open a Form and modify something on the form.
Close the Base app (using the X button or choosing File->Exit of File->Close).
The Form that was being edited closes with no prompt to save your changes.
To me this is a large bug. App should always check for changes before exiting and prompt to save if changes detected.
This is the way that Base has always was functioned. If you delete the parent container, i.e. the main Base application window it is equivalent to disposing of the connection. The child windows which represent Query, Table, Form and Report management all depend on the main Base application window.
In effect, your request is not a bug request, but a feature request to make the child windows independent of the main Base. Unfortunately, this would require quite a lot of work and many changes to the underlying code I suspect, not to mention the Base API.
From what I can recall, the child windows do not communicate their status to the parent window, so it is currently impossible for the parent to know whether anything has changed. This is why it is advisable, out of principle, to regularly click on the "Save" button of the parent window, since changes are only written to the ODB file when the user does this.
Given the current lack of developer resources available in the project for Base-related problems, it is unlikely that this will change anytime soon.
Having said all that, I have discovered another bug (related no doubt to the same behaviour, which will cause a table, query, form, report wizard to enter a loop if the parent window is closed before the wizard can complete. I will open a separate report for this.
I suppose "it has always been that way" is one way to look at it. But IMO any program that exits without checking the state of its child windows is just wrong.
I do understand that resources are limited but I believe this should still be something that is added to the list of things to tackle at some point down the road.
(In reply to comment #4)
> I do understand that resources are limited but I believe this should still be
> something that is added to the list of things to tackle at some point down the
Oh, I fully agree with you, but (1) I'm not a developer :-)), and (2) the UNO programming interface is a fairly complex beast and not always as fleshed out as one would like to be !
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Adding self to CC if not already on