Conference iosg::all-in-1_v30

2482.0. "CAB$ATTRIBUTES:CC wierdness under MH option" by GANTRY::HULL (Digital Services Delivery - Motown) Fri Mar 26 1993 17:10

We have a V2.3/2.4 app to handle BCCs on mail, now running under a V3.0 
system. The EMHEAD and EMEDHD forms have an extra scrolled field called BCC 
added at the bottom below the CC fields.  We also consolidated the PRIORITY 
and RR and DR fields on the same form at the bottom.  The .FORM_SET is 
commented out now.

The named data for CC and BCC follows.  The problem is when you Answer a 
message that had CCs on it, and do an Answer ALL, and then use MH (modify 
header) to edit anything in the CC list (never even touching the BCC area), 
it keeps all the original CCs, and ADDS the result of what your editing does 
to it.  I mention BCC here because it's the only reason the form has been 
modified.

Ie,  before using MH, I had 

 CC: Matthew T. LaDuke                    ( LADUKE )
 CC: ALL-IN-1 System Manager              ( MANAGER )

Then I use MH, and erase LaDUKE and add a different user addr., so the screen 
looks like this upon exit:

 CC: V3 Test                              ( V3TEST )
 CC: ALL-IN-1 System Manager              ( MANAGER )

then 2 RETURNS to store it all.

If you Read the msg then, it shows:


TO:  Al Hull                              ( HULL )

CC:  V3 Test                              ( V3TEST )
CC:  ALL-IN-1 System Manager              ( MANAGER )
CC:  Matthew T. LaDuke                    ( LADUKE )
CC:  ALL-IN-1 System Manager              ( MANAGER )

Somehow just editing the CC field is ADDING the old entries and new entries 
as sep. lines of data. ???????????  FOR CAB$ATTRIBUTES:CC do get oa$sel_count 
gives back 4.

I tried to TRACE this and saw nothing to explain this.  I've never seen 
anything like this happen before.  Ideas on how to fix??


;;CC;;

/PRE='GET #CASE = 2'
/OPTIONAL/SCROLL=,,,MAIL$SCL_FUNCTION:CC
/RSE_RECOG=OA$MAIL_ADD_ADDR WITH .USER = CC;GET CC = OA$SEL_BINARY_ADDRESS
/SHOW='.USER:18 "  " .ORGUNIT1:25 "  ( " .FULNAM:22 " )"'/USE_FORM=EMSREC

;;BCC;;

/PRE='GET #CASE = 2'
/OPTIONAL/SCROLL=,,,MAIL$SCL_FUNCTION:BCC
/RECOG=OA$MAIL_ADD_ADDR WITH .USER = BCC;GET BCC = OA$SEL_BINARY_ADDRESS
/SHOW='.USER:30 "( " .FULNAM:35 " )"'/USE_FORM=EMSREC
/valid=<.if bcc = "@" or bcc <=> ":" then
 display BCC does not support distribution lists else oa$val_set_valid

Hmmm...this couldn't be a problem too tough for the engineers to crack,
could it?  We had to resort to removing our customization to get  MH
working again.  We'd still like a fix for this.

	-Al - hoping someone will rise to the challenge