T.R | Title | User | Personal Name | Date | Lines |
---|
1573.2 | Attachments | IOSG::MAURICE | See below | Wed Oct 07 1992 19:23 | 6 |
| This is a known problem for documents with attachments. Another that
will hopefully make its way into the first patch.
Cheers
Stuart
|
1573.3 | If document is locked, RFD=MCD | IOSG::STANDAGE | Oink...Oink...Mooooooooooooooooooooooooooooooooo | Wed Oct 07 1992 21:11 | 20 |
| The error :
"Partial move - a card was copied but not deleted".
occurs when a user attempts to refile a document which ANOTHER user
has current in their file cabinet (that is, they are reading, editing,
or the entry is sitting in their context block). As the document is
'locked' by this other user, the copy part of the refile is successful,
but the original document fails to get deleted, and this rather nasty
error message then pops up.
Therefore, whenever you see this, two versions of the file now exist -
the original one and the one sitting at the destination of the refile.
Both these error messages (and others) have been documented in the
Distributed Sharing Option (DSO) Read Me First but they were not
described in the standard V3.0 documentation/RMF. As already said,
we're hopefully looking to resolve these in the future.
Kevin.
|
1573.5 | Access problems also could do it | CHRLIE::HUSTON | | Thu Oct 08 1992 15:41 | 12 |
| re .0
As several have said, it means that the FCS performed the move portion
o the refile, so the doc exists in the target, but for some reason or
another, the FCS could nto delete the document from its original
location.
Reasons other than already suggested for this are things like access
to the document, either the user does nto have delete access or the
FCS cannot delete it (no system delete access to it).
--Bob
|
1573.6 | | IOSG::STANDAGE | Oink...Oink...Mooooooooooooooooooooooooooooooooo | Thu Oct 08 1992 15:51 | 9 |
| Refile and delete privilege are one and the same from ALL-IN-1's
point of view, so if you didn't have delete access on the drawer
the refile would not be permitted in the first place.
However, as everyone's pointed out, there are some instances
where this message crops up.
Kevin.
|