[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

282.0. "/DATA=*MUMBLE on INDEX forms" by IRONIC::MINTZ (Mall Rat) Thu Mar 19 1992 18:39

    I'm working with an application, using the ALL-IN-1 Personal Phone
    Directory subsystem as a template.
    
    My question relates to the code on the INDEX form.  When doing any of
    the record operations, for example READ or EDIT, the code looks
    something like this:
     
    FORM PHPENT/MODE=CHANGE/DATA=*PER/SAVE=#NAME
    
    What is the purpose of the /DATA=*PER?  It seems to work just fine
    without it.  And, it looks like it does not cause record locking as
    described in note 207.
    
    Thanks in advance for your help.
    
    audrey  
T.RTitleUserPersonal
Name
DateLines
282.1Updating phantom data-setUTRTSC::BOSMANWe're just sugar mice in the rainFri Mar 20 1992 07:5411
    Audrey,
    
    Using /DATE=*PER causes to change the phantom data-set directly. If you
    doesn't do that, the index will become inconsistent. Or you have to do
    that using an extra line of code (WRITE CHANGE *PER ...).
    
    To test, invoke PHPENT form from the index and change a record that is
    also in the index (thus in the phantom data-set). You'll see that the
    index won't be updated with your new value.
    
    Sjaak.
282.2Still wonderingIRONIC::MINTZMall RatFri Mar 20 1992 16:2734
    Sjaak,
    
    Thanks for the help...but I'm still wondering...
    
    This is what my index form named data looks like:
    
    ;;OA$_MO_EDIT;;
    
    GET #MOVIE=*VIDEO.MOVIE[OA$SCROLL_ADDRESS]\
    FORM VIDEO_ENTRY/MODE=CHANGE/SAVE_START=#MOVIE\
    IFEXIT\
    CLOSE_PRIOR\
    OA$SCL_UPDATE\
    OA$SCL_REFRESH
    
    When I choose this option, the record seems to get updated in both the
    data file and the scrolled region.
    
    After I did the above, I invoked my entry form interactively from the
    INDEX form and made a change to a record.  You were right, when I
    pressed EXIT SCREEN to get back to my INDEX form, the change was not
    there.  However, when I do the same thing from the INDEX in the
    Personal Phone Directory index (where /DATA=*PER is coded), I get the
    same results.  
    
    When I invoke the ENTRY form from within the INDEX, make a change to a
    record, go to another subsystem,, come back to the Video Menu and
    Recall Index - the change I made interactively is reflected!	
    
    So....anything else to help me out on this one?
    
    Thanks.
    
    audrey 
282.3Try other operationsSHALOT::WARFORDRichard Warford @OPA DTN 393-7495Fri Mar 20 1992 19:464
    Try doing DELETEs and ADDs not changes. I think this is where the use
    of the *xxx is important.
    
    Rick