Conference iosg::all-in-1_v30

    
    Hi Arjen,
    
    Re 3),
    
    > 3) Is it correct that if you are storing and restoring an application,
    > that you have to remove from the live area, than delete and purge the
    > elements if they already exist on the receiving system, for each
    > element that you are trying to get accross?
    
    If you package Site elements, then these elements are restored in the
    Development area on the receiving system. You have to move them to Live
    to make them available to the users. So, for 'testing' purposes it's
    even the other way around. Before restoring a Site application make
    sure all elements involved are moved to the Live area (if these
    elements are ready ofcourse to be used), else move them to another
    application area tem,porarily.
    
    When packaging Base elements, the elements on the receiving side will
    be overwritten (base elements). Compare it with upgrading ALL-IN-1 2.4
    to V3.0. No need to do anything with modified versions of the element,
    except checking whether or not the modifications are still necessary
    after the Base package has been restored.
    
    That's how it works today.
    
    I'll leave the rest to more knowlegdable people.
    
    Ciao,
    
    	Simon
    
    

    <    4) It seems that the FN$COMPRESS does not take away ALL the leading
    <    blanks, it seems to leave one leading blank. Is this correct or
    <    expected behaviour?
    
    
    	Yes, depending on how you read the following in Vol 1, page 6-2:  
    	replaces multiple blank spaces and tabs with single blank spaces.  
    	Also removes leading and trailing spaces and tabs.
    
     <   5) The following bit of named data does not seem to work for my
     <   customer. It gets through the first loop but fails after that:
    
     <   .FUNC CABINET SCAN .FOLDER EQS "XYZ" AND .TITLE = "BEGINNING"
     <   .LABEL LOOP
     <   .FUNC CABINET SCAN_NEXT
    
     <   The bit where it goes wrong is on the .TITLE = "BEGINNING", where
     <   beginning is the first few characters to be validated on.
    
    
    Is this the actual code?  I have used cabinet next_scan.
    
    Tim
    

    Hi Simon and Tim,
    
    Simon,
    
     The customer had moved everything to live, but when
    they tried to import the latest version of the forms, they were told
    they already existed and the only way to sort this was to remove
    /purge/delete the live elements. Are they doing something wrong?
    
    Tim,
    
    The customer gave me that bit of code, I haven't actually tried it
    myself. Did a second operator (the .TITLE = "beginning") give you 
    any problems?
    
    Thanks so far,
    Arjen
    

    An interesting form BLANK. One field called NOTHING, and named data of
    
    	ARG/OVERLAY/POST='FORCE\OA$FLD_EXIT'
    
    We got a new version of this from the WPS-PLUS group as part of the
    V4.n kit, and as your customer observes, it's dramatically different
    from the previous version, which has a 64 character choice field, an
    area to clear of all 25 lines and named data of:
    
    	MENU/CHOICE=CHOICE/CLEAR
    
    Perhaps a note in the WPS-PLUS conference?
    
    Graham

    
    RE:-1
    
    By import you mean receive from VMS I assume?
    
    You cannot currently re-receive elements from VMS as this is considered
    a conflict.  The idea of receiving elements is to get them into SCM+
    in the first place and that's all.  To 'update' elements that already
    exist you need to package the latest version of forms into a packaged
    application and restore that, then move the forms to live.
    
    FN$COMPRESS, your right about that.  I found this a few weeks ago and 
    submitted an IPR.
    
    Mike
    
    

    The .title= "beginning" gave me no problem.  I suspect the problem
    may be in understanding how cabinet scan and cabinet next_scan work.
    
    It took me reading the functions in vol 2, 3-4 times, and lots of
    traces.
    
    
    Good Luck,
    
    Tim