I understand that requirung of "double" saving anything maybe is due to the ability of having multiple instances of the same "anything". But this is a very strange and dangerous behaviour. What I mean. Open any odb file with at least one table. Select to edit the table. (Table Design) Make any change (lets say, rename a field) Save it. Close the "Table Design" window. Now you are back to the main window of odb. Although you have saved all changes you made, when you try to close the main window the program is asking the user if he/she wants to save the changes!!! (USER ASKS:)But I already have saved all my changes!!! Which are the "new" changes that program wants me to save? This may create unpredictable results in case user has already other opened windows which he may or may not want to save.
(In reply to Ηλίας Ηλιάδης from comment #0) > (USER ASKS:)But I already have saved all my changes!!! > Which are the "new" changes that program wants me to save? If you change a table the format of the table could be affected. Saving the table in the table-design saves only the table inside the database, not the formatting of the table, which is saved inside the content.xml from the *.odb-file. Try, for example, the following: Create a table "table" with fields "ID" and "Text". Save it. Close Base, ignore second saving. Open again. The table with both fields could be used. Open again for editing. Set the default (GUI-default in the table-design) of the field "Text" to 'Hallo'. Save it in the table-design-window. Close Base and ignore second saving. Open again. The GUI-default is gone when reopening the table for editing. Open the table and put some content in it. Set the width column for "Text" much bigger. Dont save the Base-file. It's the same behavior. There are some special cases where it mustn't be saved again. But most you will do in the *.odb-file works the same way: Save a form and you have to save again the *.odb-file, because the form must be saved together with the file. Save a query - the same. Save a report - the same. Only the content, which has been saved in the database mustn't be saved again in the main-window of Base. I wouldn't call this a bug. But could be a good enhancement to save all directly, when, for example, a form is saved you haven't to press save again.
I would not consider this to be a bug either, it works as designed. Changing table or query definitions saves data in a different part of the database container file, which then has to be saved globally for the odb container. I also agree that this could be a request for enhancement, setting as such.
Maybe it's working as designed. But if the form is changing anything (anywhere) it's form's "obligation" to save it. Or, at least, inform the user that due to his actions changes had to be done elsewhere. Which I consider as a bad gui desgin, but at least user is informed that this specific form made the change and not some other from the opened so far forms.
Adding self to CC if not already on
In addition the "save button" from the BASIC IDE saves «blindly» everything. This is not in accordance with "saves data in a different part of the database container file, which then has to be saved globally for the odb container."