Bug 82110 - FILESAVE: Database does not save functions for grouping in query design window
Summary: FILESAVE: Database does not save functions for grouping in query design window
Status: RESOLVED DUPLICATE of bug 68678
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: x86 (IA32) Windows (All)
: low normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-04 02:37 UTC by rathodsa
Modified: 2014-08-14 05:18 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rathodsa 2014-08-04 02:37:21 UTC
I can make the change if I am in the SQL view query editor.  However, if I make the change in the graphical query design window, then on Save it reverts back to "no function".
Comment 1 Robert Großkopf 2014-08-12 13:07:14 UTC
Could not confirm this bug with OpenSUSE 12.3 64bit rpm Linux and LO 4.3.0.4.
If you have chosen a value or a function you have to lose set the focus to another filed. So the grouping will be accepted.
Have a look at Bug68678
Comment 2 rathodsa 2014-08-14 03:14:31 UTC
This bug exists on the Windows 7 64 bit platform. 

I tried your instructions and can confirm that your workaround is working.

I have to set the value of the function and then step off the field in order to save the change?  MS Access doesn't make me do that.

May I suggest as a 20 year IT veteran that this would not work for the average user?

The suggested functionality should be that if i change the value of the drop down list, then i should be able to save it immediately.  I should not have to use a workaround.
Comment 3 Robert Großkopf 2014-08-14 05:18:00 UTC
I have written down the workaround and the link to the original bug: Bug68678

If the workaround is working, this bug would be a duplicate of the (open) Bug68678. This buggy behavior exists since LO 4.1.

I will set this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 68678 ***