To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101782





------- Additional comments from [email protected] Thu Jul  2 
23:29:18 +0000 2009 -------
In my environment, the 2 examples of cianoz DO open correctly under 3.1.0.

My problematic .ods file does NOT open under 3.1.0 until I do the following:
1. Remove the drive mapping that leads to the linked files, AND
2. Move the offending file to a higher or lower folder level.
Neither action on its own will stop OOo 3.1.0 from hanging during file open.

Most oddly, after doing the above, I have found a situation where, after opening
the file, windows 'computer management' showed a file was being accessed using
file sharing that was not a linked file but rather a previous version of the
file I was opening that happened to be in the same folder.  At the time, I had
no mapped drive so it is unclear to me why the file would have been accessed via
sharing when the file I was opening was accessed via the local C: drive and not
via sharing.  I was able to repeat the situation a few times until I opened and
closed one or two other files.  Now I am unable to repeat this observation.

I'm not sure how relevant it is, but my .ods file, when opened under 3.0.1 
contains:
* 18 links shown under edit - links
* 26 hidden sheets with names starting with file:///P:/ (should there be more
than 18?)
* 11 hidden sheets with names Table through to Table_11 that would appear to
contain copies of tables that once were linked but no longer are.
* 3 normal sheets that I created. (The other 37 must have been created
automatically by various release versions of OOo.)
* Note that the 40 sheets exist in a random order.
* Some file:/// sheets displayed information like:
The link could not be updated.          
File:   file:///P:/Projects/Design/PCBs/RMU/BMS-R13/bms_r13Parts.sxc    
Sheet:  PCB_Assy        
* One such file:/// sheet had column B hidden so the file name and sheet were
not visible.

I hope this information gives some clues on what I could usefully try next to
further pin the issue down.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to