On Tue, 2006-04-25 at 14:23 +0300, Tomas Kuliavas wrote:
> > On Fri March 3 2006 22:37, + Richard Wright wrote:
> >> I am using version 2.0.1 OpenOffice. When I try to read files from my
> >> network at work, I get 'Microsoft visual C++ runtime library - runtime
> >> error' for   program\soffice.BIN
> >
> > Can you please test with the newly released 2.0.2 version ?
> 
> Issue can be reproduced in OpenOffice 2.0.2 and 2.0-dev (src680_m162).
> 2.0.2 shows runtime error, 2.0-dev - small window with 'The application
> cannot be started. An internal error occurred.'
> 
> Workstation running Windows XP SP2 Home or Pro with OpenOffice 2.0.2 or
> 2.0-dev can't open documents (.sxc, .ods, .xls, .doc) on read only Windows
> 98SE network share. Same issue with documents in UNC location and mapped
> network drives. If documents are copied to local disk - they can be
> opened. If files are opened using OpenOffice file open dialog - they can
> be opened. Samba or other windows xp network shares work. Word Viewer 2003
> can open shared .doc files.

Sure looks like a bug with locking. Don't know what OOo can do about
that but it pays to file an issue as this is the best way to have
problems such as this evaluated.

If you haven't already registered, do the following:

     1. To file an issue you must register with OOo by clicking the
        My Pages tab and selecting the Register link
http://www.openoffice.org/servlets/Join
     2. Fill in your information
     3. Reply to the confirmation email that will be sent to the address
        you provided. 
     4. Once you have confirmed, go to www.openoffice.org again
     5. And click on the "My Pages" tab from which you can file and find
issues. 

Thanks for bringing this to our attention. It is important that you file
any examples with the issue to ensure your need is understood.


-- 
PLEASE KEEP MESSAGES ON THE LIST.
OpenOffice.org Documentation Co-Lead
http://documentation.openoffice.org/ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to