|  |     Hi,
    
    	here are some details about what we're trying to achieve:
    
    	1)  The BLP file (VS.BLP)
    	
		GET OA$MERGE_LINE="VS - START-TEST"
		GET OA$MERGE_LINE="<&INCLUDE 'VS.TEXT'>"
		GET OA$MERGE_LINE="<&INCLUDE 'VS.A1SIXEL'>"
		GET OA$MERGE_LINE="<&INCLUDE 'VS.TEXT'>"
		GET OA$MERGE_LINE="VS - END-TEST"
    		
    	2)  The Text file (VS.TEXT)
    
    		!++
		!This is text from VS.TEXT
		!--
     	
    
    	3)  <Merge vs.blp,vs.wpl    gives the following result:
            <List vs.wpl
	--------------------------TOP---------------------------------
	GET OA$MERGE_LINE="VS - START-TEST"
	GET OA$MERGE_LINE="
	!++
	!This is text from VS.TEXT
	!--
        "
	GET OA$MERGE_LINE="
    	"
	GET OA$MERGE_LINE="
	!++
	!This is text from VS.TEXT
	!--
    	"
	GET OA$MERGE_LINE="VS - END-TEST"
        --------------------------BOTTOM---------------------------------
    
    	Changing the BLP file to 
    
		GET OA$MERGE_LINE="VS - START-TEST"
		<&INCLUDE 'VS.TEXT'>
		<&INCLUDE 'VS.A1SIXEL'>
		<&INCLUDE 'VS.TEXT'>
		GET OA$MERGE_LINE="VS - END-TEST"
    		
	leads to the following:
    
    		--------------------------TOP---------------------------------
	GET OA$MERGE_LINE="VS - START-TEST"
	!++
	!This is text from VS.TEXT
	!--
	!++
	!This is text from VS.TEXT
	!--
	GET OA$MERGE_LINE="VS - END-TEST"
        --------------------------BOTTOM---------------------------------
    
        All the mentioned files can be copied from node SCHERZ:: (48.188).
    	
    	Any help appreciated.
    	
    	Regards,
    	Viktor                
    	
    
 | 
|  |     Hi Viktor,
    
    I played around with the VS.A1SIXEL and the .blp etc.  I had the same
    problem as yourself.  To test if WPS-PLUS or ALL-IN-1 is the cause of
    the problem I gold got (Gold G) your file into a WPS-PLUS document.  I
    managed to display the Sixel file.
    
    What you need to do is to put a Start Control and an End Control in
    your blp.  For example
    
    GET OA$MERGE_LINE="VS - START-TEST"
    GET OA$MERGE_LINE="<&INCLUDE 'VS.TEXT'>"
    
    Insert code for Start Control
    
    GET OA$MERGE_LINE="<&INCLUDE 'VS.A1SIXEL'>"
    
    Insert code for End Control
    
    GET OA$MERGE_LINE="<&INCLUDE 'VS.TEXT'>"
    GET OA$MERGE_LINE="VS - END-TEST"
    
    Hopefully someone out there will enter the code required to put in the
    control blocks in a boilerplate.  Can someone tell us where all the
    boilerplate directives are documented ?
    
    Your Sixel file  contains some kind of a graph as far as I can tell, what 
    is it ?
    
    Good luck
    
    Sunil
 | 
|  |     ALL,
    
    The directives are in the write-up for the Merge function in vol 2.
    
    There are examples of start/end control blocks in this conference
    using TEXT_FILE (1411 for starters), and some in the WPS-PLUS
    conference.
    
    HTH,
    
    Tim
 | 
|  |     Hi Sunil,
    
    	thanks very much for your effort. Unfortunately, I don't know
    	either what exactly the codes are to let a boilerplate insert
    	start/end control blocks. 
    
    	There are still some questions,
    
    	o	Is it possible to insert control blocks, if yes, how?
    	o	Where can I find some documentation about this.
    	o	Why did this work under ALL-IN-1 V2.4?
    
    	Any help is well appreciated.
    	Regards,
    	Viktor 
    
    	PS:
    	Sunil, the application to which this sixel file belongs is an
    	ALL-IN-1 based project toolkit consisting of project qualifikation
    	quiz, project calculation model, report generator (where the
    	problem with the sixel file comes up) and a set of templates.
    	The sixel files contains a project impact evaluation diamond which
    	shows the relation between risk,business,financial and complexity
    	of a given project.
    
 |