<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<BR> Hi Richard:<BR>
<BR>
I think the GET on INVEST_CUR_BOOK is occuring before the PUT<BR>
on INVESTMENT so when QTP attempts the PUT on VEST_CUR_BOOK<BR>
it finds the record has changed.<BR>
<BR>
QTP trace should be able to confirm this for you.<BR>
<BR>
Regards,<BR>
Peter Bateman<BR>
<BR>> From: RWitkopp@phxa.com<BR>> To: powerh-l@lists.sowder.com<BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since<BR>> Date: Fri, 22 Jan 2010 14:24:21 -0800<BR>> <BR>> Okay, that didn't work either. I think I'm trying to do something that can't<BR>> (or shouldn't) be done.<BR>> <BR>> I think I'll just put this task in a request of its own.<BR>> <BR>> Thanks<BR>> <BR>> -----Original Message-----<BR>> From: powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com<BR>> [mailto:powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com] On Behalf Of<BR>> Richard Witkopp<BR>> Sent: Friday, January 22, 2010 11:46 AM<BR>> To: 'Knox, Dave (Carrollton, TX)'; powerh-l@lists.sowder.com<BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since<BR>> <BR>> I don't think I can do that. There's a bunch of complexity (including<BR>> another alias of investment that didn't come into play) and dozens of item<BR>> statements that I trimmed out of the example for brevity's sake.<BR>> <BR>> There was never a problem before with another aliased investment output<BR>> statement. It physically appears before the un-aliased output. Maybe by some<BR>> quirk that matters. I'll give that a try.<BR>> <BR>> -----Original Message-----<BR>> From: powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com<BR>> [mailto:powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com] On Behalf Of<BR>> Knox, Dave (Carrollton, TX)<BR>> Sent: Friday, January 22, 2010 11:01 AM<BR>> To: powerh-l@lists.sowder.com<BR>> Subject: RE:[Bulk] arghh, the dreaded Record has been changed since<BR>> <BR>> Timing issue when it retrieves aliased output records on update (to the<BR>> same file)...<BR>> <BR>> Why not one OUTPUT?<BR>> <BR>> <BR>> OUTPUT INVESTMENTS UPDATE IF T_BATCH_AP_AD = "N" or &<BR>> T_DO_ESCROW = "Y"<BR>> <BR>> ITEM INVESTMENT_STATUS OF INVESTMENT =<BR>> &<BR>> "1"<BR>> &<BR>> IF T_BATCH_AP_AD = "N" AND T_DO_ESCROW = "Y"<BR>> &<BR>> ELSE "E" IF T_BATCH_AP_AD = "N"<BR>> <BR>> IF T_DO_ESCROW = "Y"<BR>> <BR>> ITEM CUR_BOOK_VALUE OF INVEST_CUR_BOOK FINAL<BR>> &<BR>> <BR>> TOT_CAP_DTL OF SF$INFO &<BR>> IF T_DO_ESCROW = "Y"<BR>> <BR>> <BR>> <BR>> -----Original Message-----<BR>> From: powerh-l-bounces+knoxda01=unisourcelink.com@lists.sowder.com<BR>> [mailto:powerh-l-bounces+knoxda01=unisourcelink.com@lists.sowder.com] On<BR>> Behalf Of powerh-l-request@lists.sowder.com<BR>> Sent: Friday, January 22, 2010 12:36 PM<BR>> To: powerh-l@lists.sowder.com<BR>> Subject: powerh-l Digest, Vol 56, Issue 13<BR>> <BR>> Send powerh-l mailing list submissions to<BR>> powerh-l@lists.sowder.com<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> or, via email, send a message with subject or body 'help' to<BR>> powerh-l-request@lists.sowder.com<BR>> <BR>> You can reach the person managing the list at<BR>> powerh-l-owner@lists.sowder.com<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of powerh-l digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. RE:[Bulk] arghh, the dreaded Record has been changed since<BR>> you f ound it. (Richard Witkopp)<BR>> 2. RE:[Bulk] arghh, the dreaded Record has been changed since<BR>> you f ound it. (Peter Bateman)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Fri, 22 Jan 2010 10:24:47 -0800<BR>> From: "Richard Witkopp" <RWitkopp@phxa.com><BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since<BR>> you f ound it.<BR>> To: "'Ken@Langendock.com'" <Ken@Langendock.com>,<BR>> powerh-l@lists.sowder.com<BR>> Message-ID:<BR>> <FF5DC4E9EF39AB489EC56BBC4962CA8202EB6402@p28exch1.phxa.com><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Yes, it's one to one. It updated one INVESTMENT record and the error<BR>> message<BR>> occurred on the INVEST_CUR_BOOK record. Transaction processed was 1.<BR>> <BR>> <BR>> <BR>> _____ <BR>> <BR>> From: Ken Langendock [mailto:ken.langendock@rogers.com] <BR>> Sent: Friday, January 22, 2010 5:34 AM<BR>> To: Richard Witkopp; powerh-l@lists.sowder.com<BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you<BR>> found it.<BR>> <BR>> <BR>> <BR>> Are you sure your record complex is only retrieving ONE to ONE record<BR>> complex or does your link create a ONE to MANY relationship?<BR>> <BR>> <BR>> <BR>> You could always move the reading of sf$INFO to an output phase read to<BR>> be<BR>> sure.<BR>> <BR>> <BR>> <BR>> OUTPUT Sf$INFO &<BR>> <BR>> ADD &<BR>> <BR>> UPDATE &<BR>> <BR>> NOITEMS &<BR>> <BR>> IF 1 EQ 2 &<BR>> <BR>> VIAINDEX SUBSCRIPTION &<BR>> <BR>> USING FUND_#, INVESTMENT_#<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> Ken<BR>> <BR>> <BR>> <BR>> From: powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com<BR>> [mailto:powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com] On<BR>> Behalf Of Richard Witkopp<BR>> Sent: January 21, 2010 9:35 PM<BR>> To: 'powerh-l@lists.sowder.com'<BR>> Subject: [Bulk] arghh, the dreaded Record has been changed since you<BR>> found<BR>> it.<BR>> <BR>> <BR>> <BR>> I'm getting this error in QTP. I could have sworn I've used this<BR>> structure<BR>> before to dodge it.<BR>> <BR>> The T_ variables are global temps.<BR>> <BR>> I'm getting the error on invest_cur_book. I know that investment is<BR>> getting<BR>> updated because investment_status is getting updated. Fund_#,<BR>> investment_#<BR>> are unique in each file.<BR>> <BR>> I cannot just put the if condition for t_batch_ap_ad on the item<BR>> statement<BR>> for invest_cur_book because it's actually a lot more complex than this<BR>> and<BR>> I've cut it down for brevity. I pretty much need two separate outputs<BR>> for<BR>> the investment file.<BR>> <BR>> 8.40.E on VMS.<BR>> <BR>> Pseudo-code:<BR>> <BR>> ACCESS BATCH_DTL<BR>> &<BR>> <BR>> LINK FUND_# OF BATCH_DTL,<BR>> &<BR>> <BR>> INVESTMENT_# OF BATCH_DTL<BR>> &<BR>> <BR>> TO FUND_#,<BR>> &<BR>> <BR>> INVESTMENT_# OF INVESTMENT<BR>> &<BR>> <BR>> LINK FUND_# OF INVESTMENT,<BR>> &<BR>> <BR>> INVESTMENT_# OF INVESTMENT<BR>> &<BR>> <BR>> VIAIND SUBSCRIPTION TO *SF$INFO<BR>> &<BR>> <BR>> CHOOSE BATCH_# SYSTEM SYM "T_BATCH_NBR"<BR>> <BR>> OUTPUT INVESTMENT UPDATE<BR>> &<BR>> <BR>> IF T_BATCH_AP_AD = "N"<BR>> <BR>> ITEM INVESTMENT_STATUS OF INVESTMENT =<BR>> &<BR>> <BR>> "1"<BR>> &<BR>> <BR>> IF T_DO_ESCROW = "Y"<BR>> &<BR>> <BR>> ELSE "E"<BR>> <BR>> OUTPUT INVESTMENT UPDATE<BR>> &<BR>> <BR>> ALIAS INVEST_CUR_BOOK<BR>> &<BR>> <BR>> VIA FUND_# OF INVEST_CUR_BOOK,<BR>> &<BR>> <BR>> INVESTMENT_# OF INVEST_CUR_BOOK<BR>> &<BR>> <BR>> USING FUND_# OF BATCH_DTL,<BR>> &<BR>> <BR>> INVESTMENT_# OF BATCH_DTL<BR>> &<BR>> <BR>> IF T_DO_ESCROW = "Y"<BR>> <BR>> ITEM CUR_BOOK_VALUE OF INVEST_CUR_BOOK FINAL<BR>> &<BR>> <BR>> TOT_CAP_DTL OF SF$INFO<BR>> <BR>> NOTICE: The information contained in this e-mail and any attachments is<BR>> confidential and may be privileged or otherwise protected from<BR>> disclosure.<BR>> This e-mail is intended solely for the use of the named addressee. Any<BR>> other<BR>> use, printing, copying, disclosure or dissemination may be subject to<BR>> legal<BR>> restriction. If you are not the intended recipient, please contact the<BR>> sender and delete all copies including any attachments.<BR>> <BR>> No virus found in this incoming message.<BR>> Checked by AVG - www.avg.com<BR>> Version: 9.0.730 / Virus Database: 271.1.1/2637 - Release Date: 01/21/10<BR>> 14:34:00<BR>> <BR>> <BR>> NOTICE: The information contained in this e-mail and any attachments is<BR>> confidential and may be privileged or otherwise protected from<BR>> disclosure.<BR>> This e-mail is intended solely for the use of the named addressee. Any<BR>> other<BR>> use, printing, copying, disclosure or dissemination may be subject to<BR>> legal<BR>> restriction. If you are not the intended recipient, please contact the<BR>> sender and delete all copies including any attachments.<BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL:<BR>> http://lists.sowder.com/pipermail/powerh-l/attachments/20100122/cbad9ccc<BR>> /attachment-0001.htm <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Fri, 22 Jan 2010 14:35:21 -0400<BR>> From: Peter Bateman <peterbateman808@hotmail.com><BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since<BR>> you f ound it.<BR>> To: Richard Witkopp <rwitkopp@phxa.com>, PowerHouse List<BR>> <powerh-l@lists.sowder.com><BR>> Message-ID: <BAY133-W15B614C2DB3C6C57AFE2EFF9620@phx.gbl><BR>> Content-Type: text/plain; charset="windows-1252"<BR>> <BR>> <BR>> Hi All:<BR>> <BR>> <BR>> <BR>> I believe 8.40 has the QTP Trace facility I would fire that up to see<BR>> what is going on.<BR>> <BR>> <BR>> <BR>> Regards,<BR>> <BR>> Peter<BR>> <BR>> <BR>> <BR>> From: RWitkopp@phxa.com<BR>> To: Ken@Langendock.com; powerh-l@lists.sowder.com<BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you<BR>> f ound it.<BR>> Date: Fri, 22 Jan 2010 10:24:47 -0800<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> Yes, it?s one to one. It updated one INVESTMENT record and the error<BR>> message occurred on the INVEST_CUR_BOOK record. Transaction processed<BR>> was 1.<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> From: Ken Langendock [mailto:ken.langendock@rogers.com] <BR>> Sent: Friday, January 22, 2010 5:34 AM<BR>> To: Richard Witkopp; powerh-l@lists.sowder.com<BR>> Subject: RE: [Bulk] arghh, the dreaded Record has been changed since you<BR>> found it.<BR>> <BR>> Are you sure your record complex is only retrieving ONE to ONE record<BR>> complex or does your link create a ONE to MANY relationship?<BR>> <BR>> You could always move the reading of sf$INFO to an output phase read to<BR>> be sure.<BR>> <BR>> OUTPUT Sf$INFO &<BR>> ADD &<BR>> UPDATE &<BR>> NOITEMS &<BR>> IF 1 EQ 2 &<BR>> VIAINDEX SUBSCRIPTION &<BR>> USING FUND_#, INVESTMENT_#<BR>> <BR>> <BR>> Ken<BR>> <BR>> <BR>> <BR>> From: powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com<BR>> [mailto:powerh-l-bounces+ken.langendock=rogers.com@lists.sowder.com] On<BR>> Behalf Of Richard Witkopp<BR>> Sent: January 21, 2010 9:35 PM<BR>> To: 'powerh-l@lists.sowder.com'<BR>> Subject: [Bulk] arghh, the dreaded Record has been changed since you<BR>> found it.<BR>> <BR>> I'm getting this error in QTP. I could have sworn I've used this<BR>> structure before to dodge it.<BR>> <BR>> The T_ variables are global temps.<BR>> <BR>> I'm getting the error on invest_cur_book. I know that investment is<BR>> getting updated because investment_status is getting updated. Fund_#,<BR>> investment_# are unique in each file.<BR>> <BR>> I cannot just put the if condition for t_batch_ap_ad on the item<BR>> statement for invest_cur_book because it's actually a lot more complex<BR>> than this and I've cut it down for brevity. I pretty much need two<BR>> separate outputs for the investment file.<BR>> <BR>> 8.40.E on VMS.<BR>> <BR>> Pseudo-code:<BR>> <BR>> ACCESS BATCH_DTL<BR>> &<BR>> <BR>> LINK FUND_# OF BATCH_DTL,<BR>> &<BR>> <BR>> INVESTMENT_# OF BATCH_DTL<BR>> &<BR>> <BR>> TO FUND_#,<BR>> &<BR>> <BR>> INVESTMENT_# OF INVESTMENT<BR>> &<BR>> <BR>> LINK FUND_# OF INVESTMENT,<BR>> &<BR>> <BR>> INVESTMENT_# OF INVESTMENT<BR>> &<BR>> <BR>> VIAIND SUBSCRIPTION TO *SF$INFO<BR>> &<BR>> <BR>> CHOOSE BATCH_# SYSTEM SYM "T_BATCH_NBR"<BR>> <BR>> OUTPUT INVESTMENT UPDATE<BR>> &<BR>> <BR>> IF T_BATCH_AP_AD = "N"<BR>> <BR>> ITEM INVESTMENT_STATUS OF INVESTMENT =<BR>> &<BR>> <BR>> "1"<BR>> &<BR>> <BR>> IF T_DO_ESCROW = "Y"<BR>> &<BR>> <BR>> ELSE "E"<BR>> <BR>> OUTPUT INVESTMENT UPDATE<BR>> &<BR>> <BR>> ALIAS INVEST_CUR_BOOK<BR>> &<BR>> <BR>> VIA FUND_# OF INVEST_CUR_BOOK,<BR>> &<BR>> <BR>> INVESTMENT_# OF INVEST_CUR_BOOK<BR>> &<BR>> <BR>> USING FUND_# OF BATCH_DTL,<BR>> &<BR>> <BR>> INVESTMENT_# OF BATCH_DTL<BR>> &<BR>> <BR>> IF T_DO_ESCROW = "Y"<BR>> <BR>> ITEM CUR_BOOK_VALUE OF INVEST_CUR_BOOK FINAL<BR>> &<BR>> <BR>> TOT_CAP_DTL OF SF$INFO<BR>> <BR>> NOTICE: The information contained in this e-mail and any attachments is<BR>> confidential and may be privileged or otherwise protected from<BR>> disclosure. This e-mail is intended solely for the use of the named<BR>> addressee. Any other use, printing, copying, disclosure or dissemination<BR>> may be subject to legal restriction. If you are not the intended<BR>> recipient, please contact the sender and delete all copies including any<BR>> attachments.<BR>> <BR>> No virus found in this incoming message.<BR>> Checked by AVG - www.avg.com<BR>> Version: 9.0.730 / Virus Database: 271.1.1/2637 - Release Date: 01/21/10<BR>> 14:34:00<BR>> <BR>> <BR>> NOTICE: The information contained in this e-mail and any attachments is<BR>> confidential and may be privileged or otherwise protected from<BR>> disclosure. This e-mail is intended solely for the use of the named<BR>> addressee. Any other use, printing, copying, disclosure or dissemination<BR>> may be subject to legal restriction. If you are not the intended<BR>> recipient, please contact the sender and delete all copies including any<BR>> attachments.<BR>> <BR>> _________________________________________________________________<BR>> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL:<BR>> http://lists.sowder.com/pipermail/powerh-l/attachments/20100122/78c1b3a8<BR>> /attachment.htm <BR>> <BR>> ------------------------------<BR>> <BR>> -- <BR>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =<BR>> Mailing list: powerh-l@lists.sowder.com<BR>> Subscribe: &quot;subscribe&quot; in message body to<BR>> powerh-l-request@lists.sowder.com<BR>> Unsubscribe: &quot;unsubscribe &lt;password&gt;&quot; in message body to<BR>> powerh-l-request@lists.sowder.com<BR>> http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list is closed, thus to post to the list you must be a subscriber.<BR>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the<BR>> list archive at Google.<BR>> <BR>> End of powerh-l Digest, Vol 56, Issue 13<BR>> ****************************************<BR>> <BR>> <BR>> -- <BR>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =<BR>> Mailing list: powerh-l@lists.sowder.com<BR>> Subscribe: 'subscribe' in message body to powerh-l-request@lists.sowder.com<BR>> Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to<BR>> powerh-l-request@lists.sowder.com<BR>> http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list is closed, thus to post to the list you must be a subscriber.<BR>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the list<BR>> archive at Google.<BR>> <BR>> NOTICE: The information contained in this e-mail and any attachments is<BR>> confidential and may be privileged or otherwise protected from disclosure.<BR>> This e-mail is intended solely for the use of the named addressee. Any other<BR>> use, printing, copying, disclosure or dissemination may be subject to legal<BR>> restriction. If you are not the intended recipient, please contact the<BR>> sender and delete all copies including any attachments.<BR>> <BR>> -- <BR>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =<BR>> Mailing list: powerh-l@lists.sowder.com<BR>> Subscribe: 'subscribe' in message body to powerh-l-request@lists.sowder.com<BR>> Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to<BR>> powerh-l-request@lists.sowder.com<BR>> http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list is closed, thus to post to the list you must be a subscriber.<BR>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the list<BR>> archive at Google.<BR>> <BR>> NOTICE: The information contained in this e-mail and any attachments is<BR>> confidential and may be privileged or otherwise protected from disclosure.<BR>> This e-mail is intended solely for the use of the named addressee. Any other<BR>> use, printing, copying, disclosure or dissemination may be subject to legal<BR>> restriction. If you are not the intended recipient, please contact the<BR>> sender and delete all copies including any attachments.<BR>> <BR>> -- <BR>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =<BR>> Mailing list: powerh-l@lists.sowder.com<BR>> Subscribe: 'subscribe' in message body to powerh-l-request@lists.sowder.com<BR>> Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to powerh-l-request@lists.sowder.com<BR>> http://lists.sowder.com/mailman/listinfo/powerh-l<BR>> This list is closed, thus to post to the list you must be a subscriber.<BR>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the list archive at Google.<BR> <br /><hr /> <a href='' target='_new'></a></body>
</html>