Bug 66804 - EDITING: Fields linked to other file do not maintain filenames correctly producing errors.
Summary: EDITING: Fields linked to other file do not maintain filenames correctly prod...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.6.2 release
Hardware: x86 (IA32) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-10 22:51 UTC by Michael Tiernan
Modified: 2013-07-11 20:34 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 Michael Tiernan 2013-07-10 22:51:49 UTC
I have a spreadsheet (fairly simple) that uses a lookup function.

In the lookup I reference another sheet in another file and it has mixed cases. For some reason all the paths have been convered to lower-case.

The files are located in these paths:
/Users/mtiernan/Documents/All - Work/MIT:Bates:Lns/Inventory/CD_Bat_Machines/Server Equipment from Fermi.csv
/Users/mtiernan/Documents/All - Work/MIT:Bates:Lns/Inventory/CD_Bat_Machines/Server Equipment from Fermi.ods
/Users/mtiernan/Documents/All - Work/MIT:Bates:Lns/Inventory/CD_Bat_Machines/Server Equipment from Fermi.xls
/Users/mtiernan/Documents/All - Work/MIT:Bates:Lns/Inventory/CD_Bat_Machines/Units_Removed.ods

When the first items is loaded I get an error:
  https://dl.dropboxusercontent.com/u/27834209/Libreoffice-bugzilla/screen01.tiff

When I open the first spreadsheet the paths look like this:
  https://dl.dropboxusercontent.com/u/27834209/Libreoffice-bugzilla/screen02.tiff

which is incorrect. The *correct* entires should look like this:
  https://dl.dropboxusercontent.com/u/27834209/Libreoffice-bugzilla/screen03.tiff
Comment 1 m_a_riosv 2013-07-10 23:31:53 UTC
Hi Michael, thanks for reporting.

Can you try to see? if changing the option in:
Menu/Tools/Options/Load-Save/Save - Save URLs relative to file system.
helps in some way.
Comment 2 Michael Tiernan 2013-07-10 23:56:53 UTC
Will try again tomorrow evening. For safety sake I need to fix and back up my existing files and I need the time to do it.

Thanks.
Comment 3 Michael Tiernan 2013-07-11 12:33:15 UTC
Okay, first part of this is, by default the "relative" flags are on:
  https://dl.dropboxusercontent.com/u/27834209/Libreoffice-bugzilla/screen04.tiff
so that's an issue...

So, as per request, I've changed the flag and started to rewrite my formula the exact same way so that we can test what happens.

I did a series of screen shots for each step of the process starting with:
https://dl.dropboxusercontent.com/u/27834209/Libreoffice-bugzilla/Screens11.tiff
they are sequentially numbered from 11 to 17

11: Snap of formula that exists now with full paths and lower case (this is what caused me to file the bug to begin with.)
12: I chose the formula editing button and got this screen.
13: Clicked on the path part of the LOOKUP function and got this screen.
14: Selected my target as it should be. (Note paths & case)
15: Hit return to complete my selection.
16: Modified selection to include "$" no change command.
17: Clicked on the "Ok" button. ... @#$(*$%#($%&  WTF??? :)

It seems that the formula got evaporated. You'll be hard pressed to convince me that it's a feature. ;)

How's that help? Let me know what else I can do to help.
Comment 4 Michael Tiernan 2013-07-11 13:15:20 UTC
I really want to start drinking now. :(

Nothing I've been able to do has duplicated the failure. I've tried all sorts of combinations.

Relative flag on/off.
Open saying "No" to update links and resave and reopen.
Open without other file (linked to) in place. Save. Reopen.
Rewrite formulae from scratch from the keyboard without using formula editor.
FYI, Rewriting *WITH* Formula editor has its own problems.

I'm stuck. Nothing I've done has reproduced this problem. However, I'm *SURE* that the only way it could have happened, especially so completely (entire path made lower case) would be an internal action of the software, not an external force. (i.e. Operator stupidity. I'm not saying I'm not guilty of it, just not this time.)

So, in the interest of everyone. Maybe tag this as a "possible" bug so that if someone's working in the code and they come across something that they aren't sure of, this might help identify the problem.

I don't know what else to do. :(
Comment 5 Michael Tiernan 2013-07-11 13:45:01 UTC
One possible thing has occurred to me and that is it is possible that the "formula" autocorrect feature might have been activated.

If I entered the formula by hand (as I've been doing) and missed a piece of punctuation or something, the "check before save" function might have massaged the characters in the path.
Comment 6 m_a_riosv 2013-07-11 20:34:09 UTC
Thanks for your efforts.
There is not a "possible" state, and as the bugs are not deleted, we can change to resolved notabug. Please if you are not agree or you find the bug again, reopen it.