Conference iosg::all-in-1_v30

    Hi,
    
    Set your default to the site-directory that contains DEVELOP.
    Then $ COPY DEVELOP.FLB *
         $ FMS /LIB DEVELOP OA$LIB:OAFORM /FORM=MORE$SCROLL$KEYS$INDEX
         $ FMS /LIB /CREAT DEVELOP.FLB DEVELOP.FLB
    And go back to ALL-IN-1.
    
    You just hacked ALL-IN-1 but I find that this kind of forms must be
    available in all form-libs.
    
    Sjaak.

    
    Hi,
    
    The example of .-1) is correct, and we know about the wish. In V3.0 we
    probably met half way, as MORE$SCROLL$KEYS$INDEX will now be added to
    all appropriate live form libraries when it is moved to the live area.
    
    However, don't hack DEVELOP.FLB just like that. Only if you know for
    sure there are no programmers working on the system then do the manual
    hack. If there are take the (somewhat) more carefull approach:
    
    In V2.4:
    Edit CM_LOCK_LIB.SCP and replace 'DATA_FILE LOCK/ON' by 'DATA_FILE
    LOCK/ON CM$LOCK' (via CM).
    Define #CM_FILENAME to be the full specification of the DEVELOPMENT
    form library.
    Call CM_LOCK_LIB and check symbol #CM_LOCK_LIB_STATUS to see if you
    could take the lock (1 means success). If you can, then do the manual
    hack.
    After the hack, call CM_UNLOCK_LIB (from the same ALL-IN-1 session,
    else define symbol #CM_FILENAME again).
    
    In V3.0:
    Define #CM_LOCK_KEY to be the full specification of the DEVELOPMENT
    form library.
    Call CM_LOCK_LIB and check symbol #CM_LOCK_LIB_STATUS to see if you
    could take the lock (1 means success). If you can, then do the manual
    hack.
    After the hack, call CM_UNLOCK_LIB (from the same ALL-IN-1 session,
    else define symbol #CM_LOCK_KEY again).
    
    Or am I too cautious now (meaning ignoring common sense (no offense)).
    
    Ciao,
    
    	Simon
    
    
     

    Simon,
    
�                                                                In V3.0 we
�    probably met half way, as MORE$SCROLL$KEYS$INDEX will now be added to
�    all appropriate live form libraries when it is moved to the live area.
    
    I assume that you did the same with all the other .MORE screens
    (SM$MORE�� etc.)
    
    Sjaak.

    Sjaak,
    
    MORE$SCROLL$KEYS$INDEX... and it's cousins CM$MORE$SCROLL$KEYS$INDEX
    and SA$MORE$SCROLL$KEYS$INDEX ... are done in the same way.
    
    The one you specified SM$MORE$SCROLL$KEYS$INDEX isn't and I thought
    this was strange so I asked Simon when he was here and he came up with
    a good reason for it that unfortunately escapes me this early on a MOnday.
    
    Simon? I know I have it written down somewhere I just can't find it.
    
    Regards,
    
    Andrew.D.Wicks
                                            

    
    Andrew,
    
    The 'good' reason was that SM$... only appears in the MANAGER.FLB,
    while SA$... appears in ADMIN.FLB and UQM.FLB. 
    
    Sjaak, also FC$GOLD_GET has been catered for. Have a look at CM$ETYPES
    on a V3.0 system (options MGT CSZ MET I (Index)). You'll see all 4
    forms entered as 'Exception elements' next to the 2* 'Standard' element
    types. The exceptions merely deal with the 'different' situation that
    the forms appear in more than one form library, so they needed special
    processing different from the 'Standard FRM' element type.
    
    Ciao,
    
    	Simon

    Simon,
    
    Ok found then now (:==:) and of course CM$MORE... is in CM and
    CM$MANAGER and MORE$SCROLL...  is in MEMRES, OAFORM and OAN$FORMS
    
    See I was listening!
    
    Regards,
    
    Andrew.D.Wicks

    
    To be complete, now that we've started:
    
    MORE$SCROLL$KEYS$INDEX	-> OAN$FORMS, MEMRES, OAFORM
    CM$MORE$SCROLL$KEYS$INDEX	-> CM, CM$MANAGER
    SA$MORE$SCROLL$KEYS$INDEX	-> ADMIN, UQM
    FC$GOLD_E			-> CM, MEMRES, OAFORM, OAN$FORMS
    
    CIao,
    
    	Simon

    Now that we've got that sorted out ;-)!
    
    Simon (et al),
    
    Why can't we just move it? Like what are we supposed to do if for some
    reason we want to modify one of these forms?
    
    regards,
    ajb

    
    Hi,
    
    I'm not sure if I understand your question. However...
    
    When you want to modify one of these forms, just modify them like any
    other form -> Copy them from Base to Development, make the changes,
    Mark the to be Moved to the live environment, and the Maintainer will
    then Move them to live. For the Programmer and the Maintainer there are
    no additional options or things to do to process these forms. CM knows
    what to do with these forms. CM knows that when one of these forms is
    moved to live it should move it to a number of libraries. 
    
    So from a UI point of view these 4 forms are no different from ordinary
    forms, but we had a fun time writing the code to make sure the UI
    wouldn't change.  
    
    HTH,
    
    	Simon

    Hi, Simon,
    
    I couldn't copy - it gave an error. I'll not have access to the wayward
    machine until tomorrow so I'll post the error message tomorrow night.
    
    Regards,
    ajb

    
>>               <<< Note 415.9 by CESARE::EIJS "All in 1 Piece" >>>
>>          -< If for some reason you want to modify them, just do it! >-
    
>>    When you want to modify one of these forms, just modify them like any
>>    other form -> Copy them from Base to Development, make the changes,
    
    When I try this on a V3 system I get the message
    
    	'Operation not supported for this element'
    
    The same message is given if you try to Read or Print the element from
    the Access Base Elements menu.
    
    Is there some trick to this that we don't know about?
    
    Malcolm

    I just tried accessing MORE$SCROLL$KEYS$INDEX from the ABE menu in CM
    and it actually worked.

    I assume that you did a GOLD W to get more details so you might want to
    turn on tracing to see if you can determine from where this clever
    message comes.

    I am on BL123 (no letters or anything).

    Have fun,
    don

    Hi ajb, Malcolm,

    The message is the result of:

    .IF CM$ETYPES.%KEY[#CM_TYPE_KEY] EQS "" THEN GET OA$DISPLAY = CM$_INV_ELE\\

    The CWB on the menu should indicate that the element is an '(Exception)'.
    The symbol #CM_TYPE_KEY contains the key to access CM$ETYPES, which in
    your case will be 'MORE$SCROLL$KEYS$INDEX FRM <appl area>' (don't 
    fall over missing spaces). 

    Has your V3.0 system gone through a number of BL updates? It seems you'r
    missing information in CM$ETYPES.DAT, a data set which got changed
    considerably a few times during different base levels.

    Or, are you running an ALL-IN-1/British V3.0 system? In that case, did
    you read the part in the Release Notes about copying the 4 exception
    elements to their right <application area>? In my version (February 1992) 
    page 2-11 explains why and what to do.

    HTH,

	Simon