[Bulk] arghh, the dreaded Record has been changed since you f ound it.

[Peter Bateman]

From: peterbateman808 at hotmail.com
To: rwitkopp at phxa.com; powerh-l at lists.sowder.com
Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you f ound it.
Date: Fri, 22 Jan 2010 14:35:21 -0400



Hi All:
 
   I believe 8.40 has the QTP Trace facility I would fire that up to see what is going on.
 
Regards,
Peter
 


From: RWitkopp at phxa.com
To: Ken at Langendock.com; powerh-l at lists.sowder.com
Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you f ound it.
Date: Fri, 22 Jan 2010 10:24:47 -0800







Yes, it’s one to one. It updated one INVESTMENT record and the error message occurred on the INVEST_CUR_BOOK record. Transaction processed was 1.
 




From: Ken Langendock [mailto:ken.langendock at rogers.com] 
Sent: Friday, January 22, 2010 5:34 AM
To: Richard Witkopp; powerh-l at lists.sowder.com
Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you found it.
 
Are you sure your record complex is only retrieving ONE to ONE record complex or does your link create a ONE to MANY relationship?
 
You could always move the reading of sf$INFO to an output phase read to be sure.
 
OUTPUT Sf$INFO &
   ADD &
   UPDATE &
   NOITEMS &
   IF 1 EQ 2 &
  VIAINDEX SUBSCRIPTION &
  USING FUND_#, INVESTMENT_#
 
 
Ken
 


From: powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com [mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On Behalf Of Richard Witkopp
Sent: January 21, 2010 9:35 PM
To: 'powerh-l at lists.sowder.com'
Subject: [Bulk] arghh, the dreaded Record has been changed since you found it.
 I'm getting this error in QTP. I could have sworn I've used this structure before to dodge it.
The T_ variables are global temps.
I'm getting the error on invest_cur_book. I know that investment is getting updated because investment_status is getting updated. Fund_#, investment_# are unique in each file.
I cannot just put the if condition for t_batch_ap_ad on the item statement for invest_cur_book because it's actually a lot more complex than this and I've cut it down for brevity. I pretty much need two separate outputs for the investment file.
8.40.E on VMS.
Pseudo-code:
ACCESS  BATCH_DTL                                                       &
        LINK    FUND_#                  OF BATCH_DTL,                   &
                INVESTMENT_#            OF BATCH_DTL                    &
        TO      FUND_#,                                                 &
                INVESTMENT_#            OF INVESTMENT                   &
        LINK    FUND_#                  OF INVESTMENT,                  &
                INVESTMENT_#            OF INVESTMENT                   &
        VIAIND  SUBSCRIPTION            TO *SF$INFO                     &
CHOOSE  BATCH_# SYSTEM  SYM     "T_BATCH_NBR"
OUTPUT  INVESTMENT              UPDATE                                  &
        IF      T_BATCH_AP_AD   = "N"
        ITEM    INVESTMENT_STATUS       OF INVESTMENT   =               &
                "1"                                                     &
                IF      T_DO_ESCROW = "Y"                               &
                ELSE    "E"
OUTPUT  INVESTMENT              UPDATE                                  &
        ALIAS   INVEST_CUR_BOOK                                         &
                VIA     FUND_#          OF INVEST_CUR_BOOK,             &
                        INVESTMENT_#    OF INVEST_CUR_BOOK              &
                USING   FUND_#          OF BATCH_DTL,                   &
                        INVESTMENT_#    OF BATCH_DTL                    &
        IF      T_DO_ESCROW     = "Y"
        ITEM    CUR_BOOK_VALUE          OF INVEST_CUR_BOOK      FINAL   &
                TOT_CAP_DTL             OF SF$INFO
NOTICE: The information contained in this e-mail and any attachments is confidential and may be privileged or otherwise protected from disclosure. This e-mail is intended solely for the use of the named addressee. Any other use, printing, copying, disclosure or dissemination may be subject to legal restriction. If you are not the intended recipient, please contact the sender and delete all copies including any attachments.
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.730 / Virus Database: 271.1.1/2637 - Release Date: 01/21/10 14:34:00

NOTICE: The information contained in this e-mail and any attachments is confidential and may be privileged or otherwise protected from disclosure. This e-mail is intended solely for the use of the named addressee. Any other use, printing, copying, disclosure or dissemination may be subject to legal restriction. If you are not the intended recipient, please contact the sender and delete all copies including any attachments.



Spread the cheer with Messenger for mobile. Learn more. 		 	   		  
_________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20100122/3620ef22/attachment.htm