Conference iosg::all-in-1_v30

    Is the live version of the element compiled into a TXL?
    
    That might account for the difference between DFT (default - including
    TXLs) and DVF (develop first, ignore TXLs).
    
    Tony

    
    Yes, the live version of the BLP is in the TXL.
    
    Also, when directing the MERGE output to a WPL file a dump of the WPL
    file shows the NUL character. It is also possible that when printing
    the output to a printer the 'glitch' is actually the characters '{NUL}'
    overprinted on each other. It is hard to tell exactly what the
    characters are but this combination is possible.
    
    Liz

    Further...
    
    I require the output of the MERGE to be a WPL file so that I can
    maintain bolding etc. and the NUL always occurs at the end of the line.

    Further investigation reveals that I can get rid of the NUL by 
    modifying the line following the problem line in the BLP. For example if I 

    . remove a data item from the line
    . remove bolding from a piece of text
    . move the first data item 1 column to the right

    At this stage I think that the problem occurs when the MERGE is 
    formatting the line after the one that includes the NUL but it still 
    only occurs in DFT not in DVF.

    RE .1 When I trace this code the DVF version includes references to 
    Text DSAB Name:TXT$TXL_BLP. Does this mean I am referencing a BLP 
    item not currently compiled in a TXL?
         
    Does this information mean anything to you ... Liz

    It's in the TXL !!
    
    If I force the code to use the template in OA$BLP rather than 
    using the OA$TXL_SEARCH_ORDER to find the BLP the output is OK.

    If I OA$TXL_LIST the TXL version of the BLP to a file and dump the 
    output I can see the NUL character.

    So, how might this character be included in the TXL. Could there 
    be a problem with the OA$TXL_COMPILE function.

    I have two very similar BLP's and both are effected by this problem 
    in exactly the same way.
	
    Also when I OA$TXL_LIST an element the list does not clear the line
    before it displays the next line so there is additional text
    information displayed. Is this normal.

    Thanks.. Liz

It does look like a TXL compilation problem. I havent had time to look into it
but if you supply an example of a BLP which exhibits the problem, I'll see if
I can get some investigation done


thanks

eileen

	Here is a reduced version of the BLP causing the problem.

	The problem occurs at the end of the first line of ==='s.
	
	Thanks.. Liz

                      
<&BOLD>As at<&CLEAR><&TAB 17><#FRS_DATE:2>-<#FRS_DATE:2:2>-<#FRS_DATE:4:4> 
<&BOLD>Last Report Date<&CLEAR> <#CUS_LNSR_DATE:2>-<#CUS_LNSR_DATE:2:2>-<#CUS_LNSR_DATE:4:4>

<&TAB 12><&BOLD>Credit<&TAB 25>Legal Debt<&TAB 43>Usage<&TAB 56>Security<&TAB 72>Current<&CLEAR>
<&TAB 12><&BOLD>Limit<&TAB 26>Exposure<&TAB 56>Valuation<&TAB 71>Est. Loss<&CLEAR>
<&BOLD>Class 1<&CLEAR><&TAB 11><#CUS_CLASS1_LIMIT><&TAB 26><#CUS_CLASS1_LEGAL_DEBT><&TAB 41><#CUS_CLASS1_USAGE><&TAB 56><#CUS_CLASS1_SEC_VALUATION><&TAB 71><#CUS_CLASS1_EST_LOSS>
<&BOLD>Class 2<&CLEAR><&TAB 11><#CUS_CLASS2_LIMIT><&TAB 26><#CUS_CLASS2_LEGAL_DEBT><&TAB 41><#CUS_CLASS2_USAGE><&TAB 56><#CUS_CLASS2_SEC_VALUATION><&TAB 71><#CUS_CLASS2_EST_LOSS>
<&TAB 11>========<&TAB 26>========<&TAB 41>========<&TAB 56>========<&TAB 71>========
<&BOLD>Total<&CLEAR><&TAB 11><#CUS_LIMIT><&TAB 26><#CUS_LEGAL_DEBT><&TAB 41><#CUS_USAGE><&TAB 56><#CUS_SEC_VALUATION><&TAB 71><#CUS_EST_LOSS>

<&BOLD>LRD<&CLEAR><&TAB 11><#CUS_LNSR_LIMIT><&TAB 26><#CUS_LNSR_LEGAL_DEBT><&TAB 41><#CUS_LNSR_USAGE><&TAB 56><#CUS_LNSR_SEC_VALUATION><&TAB 71><#CUS_LNSR_EST_LOSS>
<&TAB 11>========<&TAB 26>========<&TAB 41>========<&TAB 56>========<&TAB 71>========
<&BOLD>Difference<&CLEAR><&TAB 11><#CUS_DIFF_LIMIT><&TAB 26><#CUS_DIFF_LEGAL_DEBT><&TAB 41><#CUS_DIFF_USAGE><&TAB 56><#CUS_DIFF_SEC_VALUATION><&TAB 71><#CUS_DIFF_EST_LOSS> 

<&TAB 11><&BOLD>Principal<&TAB 26>Specific<&TAB 39>Int. Accrued<&TAB 56>Book Debt<&CLEAR>
<&TAB 10><&BOLD>Written-Off<&TAB 26>Provision<&TAB 41>& Forgone<&TAB 56>Exposure<&CLEAR>
<&BOLD>Class 1<&CLEAR><&TAB 11><CUS_CLASS1_WRITE_DOWN><&TAB 26><CUS_CLASS1_SPEC_PROV><&TAB 41><CUS_CLASS1_INT_FORGONE><&TAB 56><CUS_CLASS1_BOOK_DEBT>
<&BOLD>Class 2<&CLEAR><&TAB 11><CUS_CLASS2_WRITE_DOWN><&TAB 26><CUS_CLASS2_SPEC_PROV><&TAB 41><CUS_CLASS2_INT_FORGONE><&TAB 56><CUS_CLASS2_BOOK_DEBT>
<&TAB 11>========<&TAB 26>========<&TAB 41>========<&TAB 56>========
<&BOLD>Total<&CLEAR><&TAB 11><CUS_WRITE_DOWN><&TAB 26><CUS_SPEC_PROV><&TAB 41><CUS_INT_FORGONE><&TAB 56><CUS_BOOK_DEBT>

<&BOLD>LRD<&CLEAR><&TAB 11><CUS_LNSR_WRITE_DOWN><&TAB 26><CUS_LNSR_SPEC_PROV><&TAB 41><CUS_LNSR_INT_FORGONE><&TAB 56><CUS_LNSR_BOOK_DEBT> 
<&TAB 11>========<&TAB 26>========<&TAB 41>========<&TAB 56>========
<&BOLD>Difference<&CLEAR><&TAB 11><CUS_DIFF_WRITE_DOWN><&TAB 26><CUS_DIFF_SPEC_PROV><&TAB 41><CUS_DIFF_INT_FORGONE><&TAB 56><CUS_DIFF_BOOK_DEBT> 
 

Liz,
	I finally got round to trying this. What version are you running? I 
cant duplicate it on ALL-IN-1 V3.


-eileen

    
    eileen
    
    This is ALL-IN-1 V2.4
    
    .. Liz