Why is this happening?

[Mike Palandri]

I have no idea if this will work, but try "final":

item despatch_no     final t_next_despatch_no




At 06:09 PM 10/29/2006, fernando.olmos at hpa.com.au wrote:
>Hi everyone...
>
>I have a subfile with the following columns and rows ...
>
>   Consignment       Order  Despatch  Despatch    Despatch    FPOS
>T_NEXT_DESPATCH_NO
>       No             No       No       Flag        Qty       DOT
>                                                              Flag
>
>   7280072119270    859468               C                 1   N
>5
>   7280072119271    859469               C                12   N
>5
>   7280072119273    859469               C                 1   N
>6
>   7280072119272    859474               H                20   N
>1
>   7280072119274    859474               C                 1   N
>2
>   7280072119274    859474               O                 8   N
>3
>   7280072119274    859474               C                 2   N
>4
>
>I have the following QTP code using the above subfile ...
>
>access *mipss1200j
>
>output despatch_actuals in isdb add
>item despatch_no     = t_next_despatch_no
>item ...
>..etc..
>
>When I run the program, I get the following results ...
>
>   Consignment       Order  Despatch
>       No             No       No
>
>
>   7280072119270    859468     5
>   7280072119271    859469     5
>   7280072119273    859469     6
>   7280072119272    859474     1
>   7280072119274    859474     4      <-- This should have been 2
>   7280072119274    859474     4      <-- This should have been 3
>   7280072119274    859474     4
>
>
>The 2nd and 3rd last rows are wrong.
>
>If the above subfile is read in row-by-row, then why is it placing the
>despatch_no value of '4' on the Order No 859474, when they should have
>been simply set with '2' and '3' respectively?
>
>There is no sort statement in the request nor any control breaks.
>
>The table I am updating, has an index only on the combination of the
>"Order No" and "Despatch No" columns. Ignore the Consignment number
>column because it is not populated into the table.
>
>???
>
>
>Thanks in advance
>**********************************************************************
>IMPORTANT
>The contents of this e-mail and its attachments are confidential and intended
>solely for the use of the individual or entity to whom they are addressed.  If
>you received this e-mail in error, please notify the HPA Postmaster, 
>postmaster at hpa.com.au,
>then delete  the e-mail.
>This footnote also confirms that this e-mail message has been swept for the
>presence of computer viruses by Ironport. Before opening or using any
>attachments, check them for viruses and defects.
>Our liability is limited to resupplying any affected attachments.
>HPA collects personal information to provide and market our services. For more
>information about use, disclosure and access see our Privacy Policy at
>www.hpa.com.au
>**********************************************************************
>
>--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l at lists.sowder.com
>Subscribe: &quot;subscribe&quot; in message body to 
>powerh-l-request at lists.sowder.com
>Unsubscribe: &quot;unsubscribe &lt;password&gt;&quot; in message body to 
>powerh-l-request at lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.
>Add 'site:lists.sowder.com powerh-l' to your search terms to search the 
>list archive at Google.