T.R | Title | User | Personal Name | Date | Lines |
---|
3924.1 | One guess, one answer | IOSG::MARSHALL | When you've got a widget, you don't need gimmicks | Mon Feb 28 1994 12:05 | 20 |
| The first problem has nothing to do with the [.DOCx] directories. I tested it
and it works on ALL-IN-1 V3.1 EFT1. So either:
a) It's a problem speciic to the Italian kit (unlikely)
b) There's something weird with the customer's setup
or
c) It's been fixed in the PFR
The second problem isn't a problem at all; that's the way it works. When you
copy a SENT document (you don't need to be SMU'ed, it's the same if you're in
your own account) the copy is given status UNSENT. This is because the copy
hasn't been sent to anyone, it's merely a copy of a message that has been sent.
It is given STATUS of UNSENT because the most likely thing you'll want to do
with a copy of a message you've sent is to make some changes and send it again.
If you copy a READ message, it will be given STATUS of COPIED, which prevents
you changing or sending it - the same as with the original READ message.
Scott
|
3924.2 | MAILworks trivia | IOSG::TALLETT | Gimmee an Alpha colour WinPad! | Tue Mar 01 1994 10:10 | 11 |
|
Interestingly, copying a READ message in MAILworks results in
another READ message. We've had complaints that TeamLinks is
inconsistent because it works one way with a MAILworks document
and the other way with an ALL-IN-1 document. Of course, if
TeamLinks made all copied READ messages into READ messages, we'd
get complaints from ALL-IN-1 customers complaining that the VT
interface was inconsistent with the Windows interface! :-)
Regards,
Paul
|
3924.3 | ALL-IN-1 behaviours ....more | MLNTSC::ZAGHI | | Fri Mar 04 1994 15:04 | 23 |
| Hi,
first of all , excuse me for the late.
I'd like to do some other considerations ....
> The first problem has nothing to do with the [.DOCx] directories. I tested it
> and it works on ALL-IN-1 V3.1 EFT1. So either: ........
Does this problem exist in ALL-IN-1 V3.0 English ? in the other words....
Is it possible that this is a ALL-IN-1 V3.0 problem ? ( I can find this problem
on my ALL-IN-1 V3.0 italian too )
> The second problem isn't a problem at all; that's the way it works. When you
> copy a SENT document (you don't need to be SMU'ed, it's the same if you're in
> your own account) the copy is given status UNSENT. This is because the copy
> hasn't been sent to anyone, it's merely a copy of a message that has been sent
Yes but is it normal that we can find the COPIED SENT DOCUMENT in [docx]
directory ??
Many thanks ,
Paolo.
|
3924.4 | As normal as it gets round here... | IOSG::MARSHALL | A glitch in reality | Fri Mar 04 1994 17:41 | 11 |
| >> Does this problem exist in ALL-IN-1 V3.0 English ?
Sorry, don't have time to find a V3.0 system and check; all the systems I have
access to are running V3.1 EFT versions.
>> but is it normal that we can find the COPIED SENT DOCUMENT in [docx]
>> directory ?
Yes.
Scott
|
3924.5 | THANK YOU | MLNTSC::ZAGHI | | Mon Mar 07 1994 09:13 | 10 |
| Hi,
well,for the second question I'll answer to the customer that this is the normal
behaviour .
For the first question I have to escalate the problem .
Thank you for your helpfull answer ,
Paolo.
|