[Libreoffice-bugs] [Bug 49052] New: formula DGET() gives #VALUE! error when fetching calculation resulting in string

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Apr 22 15:28:30 CEST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=49052

             Bug #: 49052
           Summary: formula DGET() gives #VALUE! error when fetching
                    calculation resulting in string
    Classification: Unclassified
           Product: LibreOffice
           Version: LibO 3.5.2 Release
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Spreadsheet
        AssignedTo: libreoffice-bugs at lists.freedesktop.org
        ReportedBy: marc.claes9 at scarlet.be


Created attachment 60448
  --> https://bugs.freedesktop.org/attachment.cgi?id=60448
Enter "x" in cell D2, D3, ..., or D10 & observe result in cell C15

When the DGET() formula fetches data from a cell that contains a formula THAT
RESULTS IN A STRING, the result is the #VALUE!-error. The fetched cell itself
shows the correct string value.

If the fetched cell contains a string (not a formula), the string is fetched
correctly.

So,
Cell content    Value shown in cell   Result of DGET()-formula, fetching cell
============    ===================   =======================================
Mozes           Mozes                 Mozes
3               3                     3
=1+1            2                     2
="Mo"&"zes"     Mozes                 #VALUE!

Added file shows the effect.

I did not have the opportunity of testing this (yet)
- on other hardware
- on a 32-bit OS
- on Windows (any version/word width)
- also not (yet) on other related (database) formulas, that can fetch/handle
string values, like & DCOUNTA() DCOUNT(), ...

Thanks for any interest & comments!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Libreoffice-bugs mailing list