[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2659.0. "*cal.%address[#TEMP_CALKEY] blank.." by TAV02::CHAIM (Semper ubi Sub ubi .....) Wed May 05 1993 07:52

ALL-IN-1 V2.4

A customer complained of receiving an INVFUNVAR error while attempting to edit
an event. 

Using trace I identified the problem in TMSEVE.SCP :


  !If this is the scheduler then let him edit it
    FORM EDTMTGUI
    .IF OA$FORM_DISPOSE EQS "0" THEN .EXIT
    CAL RES MEET
    .IF OA$STATUS EQS "1" -
      THEN GET OA$DISPLAY = OA$_TM_RESCHSENT \force
  !   (Event Rescheduled and notices sent)
    CAL DISP MEET #TEMP_CALKEY

****    OA$SCL_UPDATE *CAL.%address[#TEMP_CALKEY]

    OA$SCL_REFRESH
    .GOTO END


The trace shows that there is no value for *CAL.%address[#TEMP_CALKEY].
I replaced this with CAL$CALENDAR.%address[#TEMP_CALKEY] and it appears to work
fine. 

My suspicion is that the phantom data base was not yet updated with the new
reord. 

Could someone verify/contradict this suspicion? Also is this "fix" sufficient.

Thanks,

Cb.
T.RTitleUserPersonal
Name
DateLines
2659.1SIOG::T_REDMONDThoughts of an Idle MindSat May 08 1993 21:587
    Hi Chaim,
    
    If the CAL$CALENDAR.%ADDRESS DSR is picking up the right record then
    your fix is OK.... If not, it's not.  I can't see anything wrong with
    the approach here.  
    
    T
2659.2What about V3.0 ..TAV02::CHAIMSemper ubi Sub ubi .....Sun May 09 1993 06:3315
Thanks Tony,

>    
>    If the CAL$CALENDAR.%ADDRESS DSR is picking up the right record then
>    your fix is OK.... If not, it's not.  I can't see anything wrong with
>    the approach here.  
>    
It appears that it is. I'm still puzzled why *CAL.%ADDRESS is returning a
"null" value. 

How does the V3.0 code treat this issue?

Thanks,

Cb.