Issue 4880 - No warning re. file already open
Summary: No warning re. file already open
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: OOo 1.0.0
Hardware: PC All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: bettina.haberer
QA Contact: issues@sc
URL:
Keywords: rfe_eval_ok
: 3870 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-05-15 04:21 UTC by Unknown
Modified: 2013-08-07 15:12 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-05-15 04:21:37 UTC
In the spreadsheet module at least, I don't get a warning if I open a file & 
that file is already opened by another user on the network.

I think this is a necessary feature.

If it's already there it should be turned on by default.


Adrian Hicks
Comment 1 frank 2002-05-15 08:36:45 UTC
Hi Falko,

1 4 u

Frank
Comment 2 falko.tesch 2003-10-01 10:58:17 UTC
If a file is alraedy in use it would be nice to give some initial
information about its status (who opened it, why it is is read-only).
Comment 3 falko.tesch 2003-10-01 10:58:31 UTC
started
Comment 4 falko.tesch 2003-10-15 14:13:03 UTC
*** Issue 3870 has been marked as a duplicate of this issue. ***
Comment 5 modemmaker 2005-08-22 02:18:16 UTC
This issue seems to be very quiet, possibly because if done properly, it could
be very complicated.

In the meantime, how about a very simple (but less flexible) solution? When you
open a file, OO Calc could record the date stamp. Then, when you try to save
(i.e. overwrite) the file, Calc would first check if the date stamp is still the
same. If not, the user would receive a warning something like "File has been
changed by another user since opening. Do you wish to overwrite it or save to a
different file?" 
Comment 6 aziem 2006-05-08 20:03:15 UTC
*** Issue 19921 has been marked as a duplicate of this issue. ***
Comment 7 cno 2009-06-17 13:10:26 UTC
 this functionallity has been added to 3.0.0 / 3.0.1 / 3.1.0
 (sorry don't have the issues at hand)
 > set to fixed
Comment 8 cno 2009-06-19 23:46:45 UTC
 ... and close