Why is this happening?
fernando.olmos at hpa.com.au
fernando.olmos at hpa.com.au
Sun Oct 29 21:14:53 CST 2006
Yep. That did it!
In fact I was not entirely informative in the original email.
The problem was not in the despatch actuals table, but in another output
statement further dowm, which I did not mention in the email.
That 2nd output was not being referenced on a one-to-one relationship,
by the subfile, so the output was placing the *new* despatch number into
the wrong records.
Lesson: Also qualify the exact links to every table to get the correct
record per transaction!
Thanks everyone!
-----Original Message-----
From: mgo at columbus.rr.com [mailto:mgo at columbus.rr.com]
Sent: Monday, 30 October 2006 1:46 PM
To: Fernando Olmos
Subject: RE: Why is this happening?
Fernando,
Since you are updating a different file than your input, then I would
suspect it is an issue with the linkage that Powerhouse is using to
access your output file. Try specifically directing it with using and
via to explicitly specify a unique index for the output file so that it
can only find one record for each record input. Mike
-----Original Message-----
From: fernando.olmos at hpa.com.au [mailto:fernando.olmos at hpa.com.au]
Sent: Sunday, October 29, 2006 9:39 PM
To: mgo at columbus.rr.com
Subject: RE: Why is this happening?
Yes.
It made no different. I even tried initial and sorting deliberately to
set the control break at every Despatch No change. No change.
-----Original Message-----
From: mgo at columbus.rr.com [mailto:mgo at columbus.rr.com]
Sent: Monday, 30 October 2006 1:33 PM
To: Fernando Olmos
Subject: RE: Why is this happening?
Fernando,
Have you tried FINAL instead of = ?
Mike
-----Original Message-----
From: powerh-l-bounces+mgo=columbus.rr.com at lists.sowder.com
[mailto:powerh-l-bounces+mgo=columbus.rr.com at lists.sowder.com] On Behalf
Of fernando.olmos at hpa.com.au
Sent: Sunday, October 29, 2006 9:10 PM
To: powerh-l at lists.sowder.com
Cc: Peter.Hofstaetter at hpa.com.au
Subject: Why is this happening?
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: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" 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.
**********************************************************************
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
**********************************************************************
**********************************************************************
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
**********************************************************************
More information about the powerh-l
mailing list