Conference iosg::all-in-1_v30

CDA convert Library V2.0 will convert WORD documents as long they are stored in 
RTF format. 
If they are stored in RTF format, you can even use MAILbus Conversion Manager to
convert automatically and without human intervention (except setting up MCM...)

Best regards
Pierre

Hello again,

The response I received to this query when I put it in the X400MAIL conference 
was:
 DEC MAILworks supports conversion upon delivery.  That wouldn't help
 much with this case -- you want things to either be converted outbound
 if you know you're sending to an IOS user or you want IOS to convert
 it on delivery.  The latter may be possible.  I suggest you ask in the
 ALL-IN-1 conference.

Well, my theory (as described in .0) went kerbluey.
Customer attempted DECmailworks to ALL-IN-1 IOS V3.0 - filed attachment -
handling option very limited - only thing starting with an "m" is memo - NO MW
"foreign document cannot be displayed"
(I thought all this was supposed to get handles by the FOREIGN DSAB ?)

I can't see the customer wanting to purchase any more software - he doesn't 
even want to pay for CDA... :^{

Thanks & regards,

Chele

Hello and Greetings,
Customer thinks his problems may relate to his installation
He will do the CDA IVP manually & see if all is OK

Does CDAPAT011 need to be applied if they're running CDA v2 & ALL-IN-1 V3?

Thanks & regards,

Chele

    Good morning Chele,
    
    	i was running in the same question as your RE.3.
    See 1542.4 - 1542.6 for the explanation of CDA V2.0 with and w/o
    CDAPAT011.
    
    Greetings from Vienna
    Charly
    

Hello and greetings again,

The customer has installed the 1.1 patch for CDA, relinked ALL-IN-1 IOS and
installed the new images.  The problem has not gone away.  The customer wants
to know if he needs to do something else.

The problem, is (by way of a reminder from .0) as follows:
Currently what occurs is that when WORD mail without attachments is sent from
ALL-IN-1 MAIL FOR WINDOWS, it is converted to ASCII text, but is "OK".
If a WORD mail has an attachment, and is read from ALL-IN-1 IOS, the text can
be read, but the attachments get an error message "text line unsupported by
terminal type".
    
Thanks & regards,

Chele B

Hi Chele,

IOSG seem to be very busy today (as usual, they'd say!), so I'll try and keep 
it going. What are the values for Data Type and Handling of the filed 
attachment?

Just out of curiosity - what code is translating the cover note to ASCII?

(I don't think I can suggest what should happen in your case because I don't 
know how ALL-IN-1 makes a call to CDA, but an earlier reply suggested Mailbus 
Conversion Manager as a solution - have you looked at that?)

grahame

Hi Grahame,

>>Just out of curiosity - what code is translating the cover note to ASCII?
cover note == header (DECmailworks write it out automagically - I think...)

Attachment, once filed, has Data Type of FOREIGN, handling is blank

Attachment, once filed, has Data Type of FOREIGN, handling is MI
(This for an attachment where the original MS Word doc not exported to RTF?)

>>Mailbus Conversion Manager 
WHAT?? spend money? surely you jest? They've only got CDA on the world's 
longest loan arrangement - actually buying something is a bit TOO radical.
(I'll talk to their sales support bod - maybe maybe maybe they'll be interested)

Thanks & regards,

Chele B

    Hello all,
    
>>Mailbus Conversion Manager 
>WHAT?? spend money? surely you jest? They've only got CDA on the world's 
>longest loan arrangement - actually buying something is a bit TOO radical.
>(I'll talk to their sales support bod - maybe maybe maybe they'll be interested)
    
    MCM is using CDA just like ALL-IN-1 (should) do. The advantage
    is that the conversion can take place dependent on
    source/destination. 
    
>>>Just out of curiosity - what code is translating the cover note to ASCII?
>cover note == header (DECmailworks write it out automagically - I think...)
    
    Cover note is of TYPE TEXT. 
    
    Example of mail, send with MAILworks for Windows:
    Attachment tagged as RTF2 / BINARY.
    
    Drawer: MAIL  Folder: OUTBOX    Message: 5
    
    5 SCHOLLAERT           21-APR-1993  dmw win rtf2 bin als att
    5.1 TEXT TEXT          This is the cover note
    5.2 BINARY RTF2        This is the MSword (RTF) attachment 
    
>Attachment, once filed, has Data Type of FOREIGN, handling is MI
>(This for an attachment where the original MS Word doc not exported to RTF?)
    
    You have to export to RTF. CDA does not handle MI.
    
    The file type of RTF should be added to OAET.MAR (use CM)
    like described in note 1036. 
    
    Saving a WORD doc as RTF with TeamLinks shows how the ALL-IN-1
    attributes should be. Extension .RTF, FOREIGN dsab, handling RTF2.
    
    Reading the document works fine.
    
    Now my question. It should not be necessary to add a FORMAT
    entry for RTF. But when an RTF attachment arrives within ALL-IN-1,
    the format is RTF2, the DSAB is FOREIGN but the file extension is .FGN .
    So I cannot read it.
    
    What is the missing link ?
    
    Regards,
    
    Jan