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

          Priority: medium
            Bug ID: 61743
          Assignee: [email protected]
           Summary: : Wrongly Absolute Path Referencing Across Documents
          Severity: normal
    Classification: Unclassified
                OS: Windows (All)
          Reporter: [email protected]
          Hardware: Other
        Whiteboard: BSA
            Status: UNCONFIRMED
           Version: 3.6.4.3 release
         Component: Spreadsheet
           Product: LibreOffice

Problem description: 
Referencing into another Calc document does sometimes result in partly saving a
path (to a referenced file) wrongly absolute. 
The error is, of course, not visible as long as all files reside in an
unchanged directory-path. Moving to another directory unveils the problem. 
NB ALL files (in my main example 3) reside in the same directory and were moved
AT ONCE.
Strange is (in my eyes) that in a (somehow complicated) formula where 2
external references occur (one as range for an INDEX function call, the other
one as range in a MATCH fc inside the INDEX fc) the 1st one is treated
correctly, the 2nd one shows up with the absolute path of the former location. 
The same construct with similar parameters in a neighbouring cell does not
cause an error. 
Each one of the concerned references uses an external named range. The named
range in the two mentioned MATCH-parameter positions are THE SAME while one is
treated correctly and the other one wrongly. Replacement of the range-names by
direct references helps reproducible (but is not welcome). 

Steps to reproduce:
The mentioned example shows the bug reproducible.
Switching from the usage of named ranges and adressed range references and back
does reproduce the (meanwhile) expected behaviour correct/wrong.
After having switched to addressed ranges I had done some reworking. Newly
trying to return to the usage of named ranges resulted (partly) in errors.
I tried a bit to design a minimal example for the reproduction of the bug but
did not succeed till now. 
Current behavior:

Expected behavior:
As described 
My (only) example is not really slim and not really 'open', too. It uses
downloaded data that are free for use but possibly not for further
proliferation. 'Cleaning up' is not really easy. 
I give two examples taken from neighbouring cells.
After moving:
WRONG from cell E4 (second external reference):
=INDEX('file:///D:/_O_Lib_Office/_bugs/Bearbeitet_AGr_NT_MaK003.ods'#nrStellen;MATCH(E$9;'file:///d:/_o_lib_office/1_forum/5232complexmatchacrossdocumentsnt/weiter/bearbeitet_agr_nt_mak003.ods'#nrKalenderTage;0);1)
OK from cell E5:
=INDEX('file:///D:/_O_Lib_Office/_bugs/Bearbeitet_AGr_NT_MaK003.ods'#nrAGrVerse;MATCH(E$9;'file:///D:/_O_Lib_Office/_bugs/Bearbeitet_AGr_NT_MaK003.ods'#nrKalenderTage;0);6)
Before moving:
>From E4:
=INDEX('file:///D:/_O_Lib_Office/1_Forum/5232ComplexMatchAcrossDocumentsNT/weiter/Bearbeitet_AGr_NT_MaK003.ods'#nrStellen;MATCH(E$9;'file:///d:/_o_lib_office/1_forum/5232complexmatchacrossdocumentsnt/weiter/bearbeitet_agr_nt_mak003.ods'#nrKalenderTage;0);1)
>From E5:
=INDEX('file:///D:/_O_Lib_Office/1_Forum/5232ComplexMatchAcrossDocumentsNT/weiter/Bearbeitet_AGr_NT_MaK003.ods'#nrAGrVerse;MATCH(E$9;'file:///D:/_O_Lib_Office/1_Forum/5232ComplexMatchAcrossDocumentsNT/weiter/Bearbeitet_AGr_NT_MaK003.ods'#nrKalenderTage;0);

Operating System: Windows XP
Version: 3.6.4.3 release

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to