This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C0854E.F0399DE8
Content-Type: text/plain;
charset="iso-8859-1"
QTP has an edit it does during the Output stmt that doesn't like dupe keys
being accessed and updated. If it is really your intent to update the same
record twice then the workaround is to use "NOCHECK" (or is it "NO CHECK"?)
after the UPDATE on the Output stmt. If it is not your intent to update the
same record, but the dataset has multiple records per key that need to be
updated, then a refinement of your SELECT stmt should help.
Sincerely,
Nancy Tietz
-----Original Message-----
From: Lafferty, Mike [mailto:Mike.Lafferty@AIG.COM]
Sent: Tuesday, January 23, 2001 9:46 AM
To: 'powerh-l@sphere.swau.edu'
Subject: QTP Update question.....
Good morning all,
I had posted a QUICK SELECTBOX question about 3 weeks ago, on which I
am still working and making great strides, thanks to everyone's wonderful
assistance....I'll let you know how that one turns out, when I get back to
it (you all know about 'shifting gears' in the software world)....meaning
I've been taken off that to work on something else more pressing.....
In the meantime, I have turned my attention to some QTP updates....The
situation is this....It's an automobile insurance application....I link the
POLICY-NO from the subfile to the POLICY-NO of the POLICY-MASTER dataset and
update the appropriate VIN numbers (up to OCCURS 6) for that policy....while
doing this, I encountered the error message "Record has been changed since
you last found it"....This occurs when I have more than one vehicle per
policy....Each subfile record contains a POLICY-NO, a VIN and a VINTO to do
a compare....I listed some example data from the subfile below....I have
tried several alternatives including OUTPUT AT FINAL and OUTPUT AT POLICY-NO
and also some DEFINES for the array values thinking QTP was not evaluating
them properly, all to no avail.....Maybe my approach to the problem is a
little lopsided....
We're running PH version 6.09D on a HP3000 979-100.....
I think I need some help ! (tongue-in-cheek)......
SET DICT FROMDDC
REQ VINUPDT INPUT LIMIT 100000
&
ON CALCULATION ERRORS REPORT
&
ON EDIT ERRORS REPORT
SET LOCK FILE UPDATE
ACC *FROMPOLF LINK TO POLICY-MASTER LINK TO RENEW-POL-MASTER OPT
OUT POLICY-MASTER UPD ON ERRORS REPORT &
ITEM P-VEH-VIN-NUMBER(1) FINAL VIN IF P-VEH-VIN-NUMBER(1) = VINTO ELSE
&
P-VEH-VIN-NUMBER(1)
ITEM P-VEH-VIN-NUMBER(2) FINAL VIN IF P-VEH-VIN-NUMBER(2) = VINTO ELSE
&
P-VEH-VIN-NUMBER(2)
ITEM P-VEH-VIN-NUMBER(3) FINAL VIN IF P-VEH-VIN-NUMBER(3) = VINTO ELSE
&
P-VEH-VIN-NUMBER(3)
ITEM P-VEH-VIN-NUMBER(4) FINAL VIN IF P-VEH-VIN-NUMBER(4) = VINTO ELSE
&
P-VEH-VIN-NUMBER(4)
ITEM P-VEH-VIN-NUMBER(5) FINAL VIN IF P-VEH-VIN-NUMBER(5) = VINTO ELSE
&
P-VEH-VIN-NUMBER(5)
ITEM P-VEH-VIN-NUMBER(6) FINAL VIN IF P-VEH-VIN-NUMBER(6) = VINTO ELSE
&
P-VEH-VIN-NUMBER(6)
POLICY-NO VIN VINTO
1000173 1B3BE46KXHC289815 1B3BBE46KYXH89815
1000377 1P3XP24D9NN190832 1P3X924D9NN190832
1000576 1G2AF54T9L6202569 1G2AF54T926202569
1000695 1P3BP36D1HF143256 1P3PB36D1HF143236
1001335 2FTJW36L5ECA90915 2FTJW365ELA90915
1001437 1GBFG15R6T1020579 1GBFG15R6T1020597
1001618 1B3BE46D2FC201855 1B3BE462DFC201855
1001618 1G1BN53E0NR118754 1G1BN530NR118754
1002565 1C3BF66P4HX793597 1C38F66P4HX793597
1004476 1G3HY54C8L1807541 IG3HY54C8L1807541
1004654 1C3CJ51K1JG366618 1C3CJ51K1JG36661B
1004693 SAJHX6247WC815550 SAJHK6247WC815550
1004969 1FTHF25Y3GKA72854 1FTHF25Y36KA72854
1005177 1B3XA46K3PF543136 183XA46K3PF543136
1005335 WDBCB20A8DB049998 WDBCB20A8D049998
1005522 1FALP52U3SA273426 1FLAP52U3SA273426
1005527 1B7GN14M1HS423074 1876N14M1H5423074
1005635 1G1ND52J5Y6273384 161ND52J5Y6273384
1005772 1B3EJ46X9VN656093 AB3EJ46X9VN656093
------_=_NextPart_001_01C0854E.F0399DE8
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
QTP Update question.....
QTP=20
has an edit it does during the Output stmt that doesn't like dupe keys =
being=20
accessed and updated. If it is really your intent to update the =
same=20
record twice then the workaround is to use "NOCHECK" (or is =
it=20
"NO CHECK"?) after the UPDATE on the Output stmt. If it =
is not=20
your intent to update the same record, but the dataset has multiple =
records per=20
key that need to be updated, then a refinement of your SELECT stmt =
should=20
help.
Sincerely,
Nancy Tietz
-----Original Message-----
From: Lafferty, Mike=20
[mailto:Mike.Lafferty@AIG.COM]
Sent: Tuesday, January 23, =
2001=20
9:46 AM
To: 'powerh-l@sphere.swau.edu'
Subject: =
QTP=20
Update question.....
Good morning all,
I had posted a QUICK SELECTBOX =
question=20
about 3 weeks ago, on which I am still working and making great =
strides,=20
thanks to everyone's wonderful assistance....I'll let you know how =
that one=20
turns out, when I get back to it (you all know about 'shifting =
gears' in the=20
software world)....meaning I've been taken off that to work on =
something=20
else more pressing.....
In the meantime, I have turned my =
attention to=20
some QTP updates....The situation is this....It's an automobile =
insurance=20
application....I link the POLICY-NO from the subfile to the =
POLICY-NO of the=20
POLICY-MASTER dataset and update the appropriate VIN numbers (up to =
OCCURS=20
6) for that policy....while doing this, I encountered the error =
message=20
"Record has been changed since you last found it"....This =
occurs=20
when I have more than one vehicle per policy....Each subfile record =
contains=20
a POLICY-NO, a VIN and a VINTO to do a compare....I listed some =
example data=20
from the subfile below....I have tried several alternatives =
including OUTPUT=20
AT FINAL and OUTPUT AT POLICY-NO and also some DEFINES for the =
array values=20
thinking QTP was not evaluating them properly, all to no =
avail.....Maybe my=20
approach to the problem is a little lopsided....
We're running PH version 6.09D on a =
HP3000=20
979-100.....
I think I need some help !=20
(tongue-in-cheek)......
SET DICT=20
=
FROMDDC =
; =
; =
; =
; =20
REQ VINUPDT INPUT LIMIT=20
=
100000 =
=
=
=20
&
&nb=
sp; ON=20
CALCULATION ERRORS=20
=
REPORT =
=
=
=20
&
&nb=
sp; ON=20
EDIT ERRORS REPORT
SET LOCK =
FILE=20
UPDATE
ACC *FROMPOLF LINK =
TO=20
POLICY-MASTER LINK TO RENEW-POL-MASTER OPT
OUT POLICY-MASTER UPD ON ERRORS =
REPORT=20
&
=20
ITEM P-VEH-VIN-NUMBER(1) FINAL VIN IF=20
P-VEH-VIN-NUMBER(1) =3D VINTO ELSE &
=
P-VEH-VIN-NUMBER(1)=20
ITEM P-VEH-VIN-NUMBER(2) =
FINAL=20
VIN IF P-VEH-VIN-NUMBER(2) =3D VINTO ELSE =
&=20
=20
P-VEH-VIN-NUMBER(2)
=
ITEM=20
P-VEH-VIN-NUMBER(3) FINAL VIN IF =
P-VEH-VIN-NUMBER(3)=20
=3D VINTO ELSE &
=
P-VEH-VIN-NUMBER(3)=20
ITEM P-VEH-VIN-NUMBER(4) =
FINAL=20
VIN IF P-VEH-VIN-NUMBER(4) =3D VINTO ELSE =
&=20
=20
P-VEH-VIN-NUMBER(4)
=
ITEM=20
P-VEH-VIN-NUMBER(5) FINAL VIN IF =
P-VEH-VIN-NUMBER(5)=20
=3D VINTO ELSE &
=
P-VEH-VIN-NUMBER(5)=20
ITEM P-VEH-VIN-NUMBER(6) =
FINAL=20
VIN IF P-VEH-VIN-NUMBER(6) =3D VINTO ELSE =
&=20
=20
P-VEH-VIN-NUMBER(6)
POLICY-NO =20
=
VIN &nb=
sp; =20
VINTO
=
1000173 =20
1B3BE46KXHC289815 1B3BBE46KYXH89815
1000377 =
1P3XP24D9NN190832 =20
1P3X924D9NN190832
=20
1000576 1G2AF54T9L6202569 =
1G2AF54T926202569=20
=
1000695 =20
1P3BP36D1HF143256 1P3PB36D1HF143236
1001335 =
2FTJW36L5ECA90915 =20
2FTJW365ELA90915
=20
1001437 1GBFG15R6T1020579 =
1GBFG15R6T1020597=20
1001618 =20
1B3BE46D2FC201855 1B3BE462DFC201855
1001618 =20
1G1BN53E0NR118754 1G1BN530NR118754
1002565 =
1C3BF66P4HX793597 =20
1C38F66P4HX793597
=20
1004476 1G3HY54C8L1807541 =
IG3HY54C8L1807541=20
=
1004654 =20
1C3CJ51K1JG366618 1C3CJ51K1JG36661B
1004693 =
SAJHX6247WC815550 =20
SAJHK6247WC815550
=20
1004969 1FTHF25Y3GKA72854 =
1FTHF25Y36KA72854=20
=
1005177 =20
1B3XA46K3PF543136 183XA46K3PF543136
1005335 =
WDBCB20A8DB049998 =20
WDBCB20A8D049998
=20
1005522 1FALP52U3SA273426 =
1FLAP52U3SA273426=20
=
1005527 =20
1B7GN14M1HS423074 1876N14M1H5423074
1005635 =
1G1ND52J5Y6273384 =20
161ND52J5Y6273384
=20
1005772 1B3EJ46X9VN656093 =
AB3EJ46X9VN656093=20