backout message in QUICK
Alan and Vicki
vical1 at eastlink.ca
Thu Dec 18 17:17:50 CST 2008
Martyn, I have seen this before and it would be helpful if you could provide
a bit more info about what the users are doing before they use the designer
procedure 99 and what exactly the designer procedure is doing.
In order to run the batch job, are they first doing an UPDATE STAY or are
you somehow forcing a put (or pushing and update) somewhere?
When I have run across this before, it's often becuase of a forced PUT on a
record outside the update procedure, or a missed PUT. Debugging in the
fields' INPUT procedure probably wouldn't help too much -- the record buffer
status may very well be ALTEREDRECORD FALSE at that point, but once it gets
past the edit procedure and into the process or output, it may have changed
to ALTEREDRECORD TRUE. To really trap it, I would try an info statement in
an exit procedure and see what it's telling you. And as you've been told by
others, there is no way to override it.
If memory serves, "DEFAULT" on a field statement does not change the record
status (and I'm pretty it only kicks when NEWRECORD is true so on a find, it
shouldn't make any difference at all) so I don't imagine it's that, and if
it is only a temp field, it also should not be altering the record status.
If you can provide more info, I may be able to think it through and come up
with some suggestions, and code snippets from the designer procedure (or
field statement) for the temp field as well as any procedures where there is
PUT would be helpful as well.
Good luck, Martyn!
Vicki
----- Original Message -----
From: <powerh-l-request at lists.sowder.com>
To: <powerh-l at lists.sowder.com>
Sent: Thursday, December 18, 2008 6:32 PM
Subject: powerh-l Digest, Vol 43, Issue 13
> Send powerh-l mailing list submissions to
> powerh-l at lists.sowder.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sowder.com/mailman/listinfo/powerh-l
> or, via email, send a message with subject or body 'help' to
> powerh-l-request at lists.sowder.com
>
> You can reach the person managing the list at
> powerh-l-owner at lists.sowder.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of powerh-l digest..."
>
>
> Today's Topics:
>
> 1. RE:powerh-l Digest, Vol 43, Issue 12 (Clifford Zivi)
> 2. The current data will be lost. Repeat the action if this is
> okay (Thomson, Martyn EDUC:EX)
> 3. RE:[Bulk] The current data will be lost. Repeat the action if
> this is okay (Ken Langendock)
> 4. RE:[Bulk] The current data will be lost. Repeat the action if
> this is okay (Thomson, Martyn EDUC:EX)
> 5. RE:[Bulk] The current data will be lost. Repeat the action if
> thisis okay (David Morrison)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Dec 2008 13:57:04 -0500
> From: "Clifford Zivi" <cliffordzivi at verizon.net>
> Subject: RE: powerh-l Digest, Vol 43, Issue 12
> To: <powerh-l at lists.sowder.com>
> Message-ID: <3D1382A0833848CCAB7FD03FD3BE9F78 at Moms>
> Content-Type: text/plain; charset=us-ascii
>
> Avoiding the "record has been changed..." can be bothersome...
>
> You might try introducing your own sort key. Sometimes you can build your
> own sort key by using the data in the records as in:
> DEFINE SORT-KEY CHAR*80 = FIELD1 + FIELD2 + FIELD3 + FIELD4 + FIELD5
> SORT ON SORT-KEY
>
> Or just number the records and use the numbers in some way to help you
> figure out when to update.
>
>
>
>
> Thank you,
>
> Clifford Zivi
> -----Original Message-----
> From: powerh-l-bounces+cliffordzivi=verizon.net at lists.sowder.com
> [mailto:powerh-l-bounces+cliffordzivi=verizon.net at lists.sowder.com] On
> Behalf Of powerh-l-request at lists.sowder.com
> Sent: Thursday, December 18, 2008 1:00 PM
> To: powerh-l at lists.sowder.com
> Subject: powerh-l Digest, Vol 43, Issue 12
>
> Send powerh-l mailing list submissions to
> powerh-l at lists.sowder.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sowder.com/mailman/listinfo/powerh-l
> or, via email, send a message with subject or body 'help' to
> powerh-l-request at lists.sowder.com
>
> You can reach the person managing the list at
> powerh-l-owner at lists.sowder.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of powerh-l digest..."
>
>
> Today's Topics:
>
> 1. Re:powerh-l Digest, Vol 43, Issue 10 - Agree with Gavin
> (Alan and Vicki)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Dec 2008 00:05:59 -0400
> From: Alan and Vicki <vical1 at eastlink.ca>
> Subject: Re: powerh-l Digest, Vol 43, Issue 10 - Agree with Gavin
> To: powerh-l at lists.sowder.com
> Message-ID: <C2C4685A66DF4E82B1D13E8B7A3367FE at VickiRobertsPC>
> Content-Type: text/plain; format=flowed; charset=iso-8859-1;
> reply-type=original
>
> Agree with Gavin - not sure why you're putting an alias on your output
> file -- QTP is now trying to find a linkage to it becuase it has to create
> separate record buffers -- just drop the alias and allow it to update at
> every record read (should also be faster). It is not creating any control
> breaks because you are not using a choose or a sort -- it will just update
> every record it reads....
>
> Try it and let us know how it works!
>
> Vicki
>
> ----- Original Message -----
> From: <powerh-l-request at lists.sowder.com>
> To: <powerh-l at lists.sowder.com>
> Sent: Wednesday, December 17, 2008 2:20 PM
> Subject: powerh-l Digest, Vol 43, Issue 10
>
>
>> Send powerh-l mailing list submissions to
>> powerh-l at lists.sowder.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.sowder.com/mailman/listinfo/powerh-l
>> or, via email, send a message with subject or body 'help' to
>> powerh-l-request at lists.sowder.com
>>
>> You can reach the person managing the list at
>> powerh-l-owner at lists.sowder.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of powerh-l digest..."
>>
>>
>> Today's Topics:
>>
>> 1. RE:[Bulk] Help with QTP UPDATE (Lloyd, Gavin)
>> 2. RE:[Bulk] Help with QTP UPDATE (Peter Bateman)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 17 Dec 2008 18:10:23 -0000
>> From: "Lloyd, Gavin" <gavin.lloyd at fmglobal.com>
>> Subject: RE: [Bulk] Help with QTP UPDATE
>> To: "vamsi krishna" <vamsi.coe at gmail.com>, <powerh-l at lists.sowder.com>
>> Message-ID:
>> <C34A9B9BCDF37D4DA35BDCA5548A47D47FB85B at WINDEXCHP17.corp.fmglobal.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Correct me if I'm wrong but isn't the answer as simple as taking the
>> alias off the output command:
>>
>>
>>
>> ACCESS OPTICLEN
>> &
>>
>> LINK CUN
>> &
>>
>> TO CUN OF *$PIC_DATA/OPBEUROD_S
>> &
>>
>> LINK CRY OF OPBEUROD_S
>> &
>>
>> TO CURR-CODE OF IPTIEURO
>>
>>
>>
>> SELECT IF CLAIM-CURR="SKK"
>>
>>
>>
>> OUTPUT OPTICLEN UPDATE
>>
>> ITEM CLAIM-CURR OF CLEN_UPD ="EUR"
>>
>>
>>
>> This way you will directly update the records that are being read rather
>> than linking back to the record which is what the alias makes QTP do.
>> My Powerhouse is getting rusty these days so excuse me if I've given
>> dodgy advice!
>>
>>
>>
>> Regards,
>> Gavin.
>>
>>
>>
>> From: Ken Langendock [mailto:ken.langendock at rogers.com]
>> Sent: 17 December 2008 15:51
>> To: 'vamsi krishna'; powerh-l at lists.sowder.com
>> Cc: 'mRiDuLa'
>> Subject: RE: [Bulk] Help with QTP UPDATE
>>
>>
>>
>> The problem is you are creating a record complex that may result in the
>> same record being ready to update more than once.
>>
>>
>>
>> What you need to do is get the record complex down to One in and One
>> out.
>>
>> Use output phase reading and move your select statement. And QUALIFY
>> YOUR STATEMENTS
>>
>>
>>
>> Ken
>>
>>
>>
>> ACCESS OPTICLEN
>>
>>
>>
>> OUTPUT *$PIC_DATA/OPBEUROD_S &
>>
>> ADD &
>>
>> UPDATE &
>>
>> NOITEMS &
>>
>> IF 1 EQ 2 &
>>
>> VIA CUN &
>>
>> USING CUN OF OPTICLEN
>>
>>
>>
>>
>>
>> OUTPUT IPTIEURO &
>>
>> ADD &
>>
>> UPDATE &
>>
>> NOITEMS &
>>
>> IF 1 EQ 2 &
>>
>> VIA CURR-CODE &
>>
>> USING CRY OF OPBEUROD_S
>>
>>
>>
>>
>>
>> OUTPUT OPTICLEN &
>>
>> ALIAS CLEN_UPD &
>>
>> UPDATE &
>>
>> IF CLAIM-CURR OF IPTIEURO = "SKK"
>>
>>
>>
>> ITEM CLAIM-CURR OF CLEN_UPD FINAL "EUR"
>>
>>
>>
>>
>>
>> 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 vamsi krishna
>> Sent: December 17, 2008 9:07 AM
>> To: powerh-l at lists.sowder.com
>> Cc: mRiDuLa
>> Subject: [Bulk] Help with QTP UPDATE
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I need to update an indexed file which has no unique key, but all
>> "repeating primary" and "repeating alternate" indexes.
>>
>>
>>
>>
>>
>> When i compile the program, I get the following warning:
>>
>> *W* Linkage should be via a unique key/index if the file is output only.
>>
>>
>>
>> Program is something like this:
>>
>>
>>
>> ACCESS OPTICLEN
>> &
>>
>> LINK CUN
>> &
>>
>> TO CUN OF *$PIC_DATA/OPBEUROD_S
>> &
>>
>> LINK CRY OF OPBEUROD_S
>> &
>>
>> TO CURR-CODE OF IPTIEURO
>>
>>
>>
>> SELECT IF CLAIM-CURR="SKK"
>>
>>
>>
>> OUTPUT OPTICLEN ALIAS CLEN_UPD UPDATE
>>
>> ITEM CLAIM-CURR OF CLEN_UPD ="EUR"
>>
>>
>>
>> I realize when the QTP runs, the control breaks are set on the primary
>> index by default, and the output update runs on next unique value of
>> repeating index.
>>
>> So, all the needed records in the selection are not updated.
>>
>> It would be of great help if I can set a control break so that every
>> record in selection is updated.
>>
>> Correct me if I am going anywhere, or any other perfect way of updating
>> such files.
>>
>> We have PowerHouse 8.43.D on Solaris SunOS.
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> Regards,
>>
>> Vamsi
>>
>> --
>> "Nothing is impossible as impossible itself says i m possible"
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG.
>> Version: 7.5.552 / Virus Database: 270.9.18/1852 - Release Date:
>> 16/12/2008 6:11 PM
>>
>>
>>
>> No virus found in this outgoing message.
>> Checked by AVG.
>> Version: 7.5.552 / Virus Database: 270.9.18/1852 - Release Date:
>> 16/12/2008 6:11 PM
>>
>>
>>
>> Registered No. 755780 England
>> Registered Office: FM Insurance Company Limited
>> 1 Windsor Dials, Windsor,
>> Berkshire, UK, SL4 1RS
>> Regulated by the Financial Services Authority.
>> VAT No. G.B.: 792 4276 02
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>>
> http://lists.sowder.com/pipermail/powerh-l/attachments/20081217/285a775f/att
> achment-0001.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 17 Dec 2008 14:20:12 -0400
>> From: Peter Bateman <peterbateman808 at hotmail.com>
>> Subject: RE: [Bulk] Help with QTP UPDATE
>> To: vamsi krishna <vamsi.coe at gmail.com>, PowerHouse List
>> <powerh-l at lists.sowder.com>
>> Cc: mridulap2003 at gmail.com
>> Message-ID: <BAY133-W4117B67C10AD89036000ABF9F20 at phx.gbl>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>>
>> Hi Vamsi
>>
>> Is there a unique combination of index and other item values?
>>
>> If so you can specify an access path with a select on it!
>>
>> e.g.
>>
>> OUTPUT OPTICLEN &
>> ALIAS CLEN_UPD &
>> UPDATE &
>> VIA <key item> USING <key Value> &
>> IF CLAIM-CURR OF IPTIEURO = "SKK"
>>
>> SELECT CLEN_UPD IF <other item> = <other item value>
>>
>> ITEM CLAIM-CURR OF CLEN_UPD FINAL "EUR"
>>
>> Regards,
>> Peter Bateman
>>
>>
>>
>>
>> From: ken.langendock at rogers.comTo: vamsi.coe at gmail.com;
>> powerh-l at lists.sowder.comSubject: RE: [Bulk] Help with QTP UPDATEDate:
>> Wed, 17 Dec 2008 10:50:48 -0500CC: mridulap2003 at gmail.com
>>
>>
>>
>> The problem is you are creating a record complex that may result in the
>> same record being ready to update more than once.
>>
>> What you need to do is get the record complex down to One in and One out.
>> Use output phase reading and move your select statement. And QUALIFY YOUR
>> STATEMENTS
>>
>> Ken
>>
>> ACCESS OPTICLEN
>>
>> OUTPUT *$PIC_DATA/OPBEUROD_S &
>> ADD &
>> UPDATE &
>> NOITEMS &
>> IF 1 EQ 2 &
>> VIA CUN &
>> USING CUN OF OPTICLEN
>>
>>
>> OUTPUT IPTIEURO &
>> ADD &
>> UPDATE &
>> NOITEMS &
>> IF 1 EQ 2 &
>> VIA CURR-CODE &
>> USING CRY OF OPBEUROD_S
>>
>>
>> OUTPUT OPTICLEN &
>> ALIAS CLEN_UPD &
>> UPDATE &
>> IF CLAIM-CURR OF IPTIEURO = "SKK"
>>
>> ITEM CLAIM-CURR OF CLEN_UPD FINAL "EUR"
>>
>>
>>
>> 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 vamsi krishnaSent: December 17, 2008 9:07 AMTo:
>> powerh-l at lists.sowder.comCc: mRiDuLaSubject: [Bulk] Help with QTP UPDATE
>>
>> Hi All,
>>
>>
>>
>> I need to update an indexed file which has no unique key, but all
>> "repeating primary" and "repeating alternate" indexes.
>>
>>
>>
>>
>>
>> When i compile the program, I get the following warning:
>>
>>
>> *W* Linkage should be via a unique key/index if the file is output only.
>>
>>
>>
>> Program is something like this:
>>
>>
>>
>>
>>
>> ACCESS OPTICLEN &
>>
>> LINK CUN &
>>
>> TO CUN OF *$PIC_DATA/OPBEUROD_S &
>>
>> LINK CRY OF OPBEUROD_S &
>>
>> TO CURR-CODE OF IPTIEURO
>>
>>
>>
>>
>> SELECT IF CLAIM-CURR="SKK"
>>
>>
>>
>> OUTPUT OPTICLEN ALIAS CLEN_UPD UPDATE
>>
>>
>> ITEM CLAIM-CURR OF CLEN_UPD ="EUR"
>>
>>
>>
>> I realize when the QTP runs, the control breaks are set on the primary
>> index by default, and the output update runs on next unique value of
>> repeating index.
>>
>> So, all the needed records in the selection are not updated.
>>
>> It would be of great help if I can set a control break so that every
>> record in selection is updated.
>>
>> Correct me if I am going anywhere, or any other perfect way of updating
>> such files.
>>
>> We have PowerHouse 8.43.D on Solaris SunOS.
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> Regards,
>>
>> Vamsi-- "Nothing is impossible as impossible itself says i m possible"
>>
>> No virus found in this incoming message.Checked by AVG.Version: 7.5.552 /
>> Virus Database: 270.9.18/1852 - Release Date: 16/12/2008 6:11 PM
>> No virus found in this outgoing message.Checked by AVG.Version: 7.5.552 /
>> Virus Database: 270.9.18/1852 - Release Date: 16/12/2008 6:11 PM
>> _________________________________________________________________
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>>
> http://lists.sowder.com/pipermail/powerh-l/attachments/20081217/f92039e7/att
> achment.htm
>>
>> ------------------------------
>>
>> --
>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>> 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.
>>
>> End of powerh-l Digest, Vol 43, Issue 10
>> ****************************************
>>
>
>
>
>
> ------------------------------
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
> End of powerh-l Digest, Vol 43, Issue 12
> ****************************************
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 18 Dec 2008 11:33:26 -0800
> From: "Thomson, Martyn EDUC:EX" <martyn.thomson at gov.bc.ca>
> Subject: The current data will be lost. Repeat the action if this is
> okay
> To: <powerh-l at lists.sowder.com>
> Message-ID: <3AF6BC723480024198464C4B8A020695275B8C at KINDLE.idir.bcgov>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Listers,
> Have a screen where user retrieves existing records for
> viewing/update/entry. They can enter "99" to go to a temporary field and
> submit a batch job to process the records saved/viewed.
> If they attempt to backout from the temp field get message "The current
> data will be lost. Repeat the action if this is okay".
>
> Why is this if they have not entered/changed any data or have already
> committed changes? ALTEREDRECORD is FALSE.
> Is this just an automatic warning whenever "^" is entered?
> Is there any way to suppress this msg when it's not relevant?
>
> TIA for any advice.
> Martyn
> PH 7.10G1; OpenVMS Alpha V8.3, Oracle Rdb V7.2-311
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 18 Dec 2008 15:25:43 -0500
> From: "Ken Langendock" <ken.langendock at rogers.com>
> Subject: RE: [Bulk] The current data will be lost. Repeat the action
> if this is okay
> To: "'Thomson, Martyn EDUC:EX'" <martyn.thomson at gov.bc.ca>,
> <powerh-l at lists.sowder.com>
> Message-ID: <000c01c9614e$cd743c20$685cb460$@langendock at rogers.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I'll bet you have a let statement somewhere that you think is to a temp
> but
> isn't or something similar.
> I have also found this using an ITEM xxxx FINAL "something".
> Normally this doesn't do anything to records status....but As part of a
> cluster it WILL CHANGE THE RECORD STATUS.
>
> You can't suppress any messages like that, they are there an integral part
> of PH.
>
> Ken
>
> -----Original Message-----
> 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 Thomson, Martyn EDUC:EX
> Sent: December 18, 2008 2:33 PM
> To: powerh-l at lists.sowder.com
> Subject: [Bulk] The current data will be lost. Repeat the action if this
> is
> okay
>
> Hi Listers,
> Have a screen where user retrieves existing records for
> viewing/update/entry. They can enter "99" to go to a temporary field and
> submit a batch job to process the records saved/viewed.
> If they attempt to backout from the temp field get message "The current
> data
> will be lost. Repeat the action if this is okay".
>
> Why is this if they have not entered/changed any data or have already
> committed changes? ALTEREDRECORD is FALSE.
> Is this just an automatic warning whenever "^" is entered?
> Is there any way to suppress this msg when it's not relevant?
>
> TIA for any advice.
> Martyn
> PH 7.10G1; OpenVMS Alpha V8.3, Oracle Rdb V7.2-311
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.552 / Virus Database: 270.9.19/1854 - Release Date:
> 17/12/2008
> 7:21 PM
>
>
> No virus found in this outgoing message.
> Checked by AVG.
> Version: 7.5.552 / Virus Database: 270.9.19/1854 - Release Date:
> 17/12/2008
> 7:21 PM
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 18 Dec 2008 14:15:05 -0800
> From: "Thomson, Martyn EDUC:EX" <martyn.thomson at gov.bc.ca>
> Subject: RE: [Bulk] The current data will be lost. Repeat the action
> if this is okay
> To: <Ken at Langendock.com>, <powerh-l at lists.sowder.com>
> Message-ID: <3AF6BC723480024198464C4B8A020695275B8D at KINDLE.idir.bcgov>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I am using a cluster so removed all LETs - no difference. No ITEM
> statements.
> Do DEFAULT option on FIELD statements have the same effect?
> Also added an INPUT proc to the temp field to trap it in debug. The
> predefs ALTEREDRECORD, NEWRECORD were both false.
>
>
> -----Original Message-----
> From: Ken Langendock [mailto:ken.langendock at rogers.com]
> Sent: Thu 18-Dec-08 12:25 PM
> To: Thomson, Martyn EDUC:EX; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] The current data will be lost. Repeat the action if
> this is okay
>
> I'll bet you have a let statement somewhere that you think is to a temp
> but
> isn't or something similar.
> I have also found this using an ITEM xxxx FINAL "something".
> Normally this doesn't do anything to records status....but As part of a
> cluster it WILL CHANGE THE RECORD STATUS.
>
> You can't suppress any messages like that, they are there an integral part
> of PH.
>
> Ken
>
> -----Original Message-----
> 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 Thomson, Martyn EDUC:EX
> Sent: December 18, 2008 2:33 PM
> To: powerh-l at lists.sowder.com
> Subject: [Bulk] The current data will be lost. Repeat the action if this
> is
> okay
>
> Hi Listers,
> Have a screen where user retrieves existing records for
> viewing/update/entry. They can enter "99" to go to a temporary field and
> submit a batch job to process the records saved/viewed.
> If they attempt to backout from the temp field get message "The current
> data
> will be lost. Repeat the action if this is okay".
>
> Why is this if they have not entered/changed any data or have already
> committed changes? ALTEREDRECORD is FALSE.
> Is this just an automatic warning whenever "^" is entered?
> Is there any way to suppress this msg when it's not relevant?
>
> TIA for any advice.
> Martyn
> PH 7.10G1; OpenVMS Alpha V8.3, Oracle Rdb V7.2-311
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.552 / Virus Database: 270.9.19/1854 - Release Date:
> 17/12/2008
> 7:21 PM
>
>
> No virus found in this outgoing message.
> Checked by AVG.
> Version: 7.5.552 / Virus Database: 270.9.19/1854 - Release Date:
> 17/12/2008
> 7:21 PM
>
>
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 18 Dec 2008 14:32:16 -0800
> From: "David Morrison" <DMorrison at mcbrideinc.com>
> Subject: RE: [Bulk] The current data will be lost. Repeat the action
> if thisis okay
> To: "Thomson, Martyn EDUC:EX" <martyn.thomson at gov.bc.ca>,
> <Ken at Langendock.com>, <powerh-l at lists.sowder.com>
> Message-ID:
> <FD4DEFEC04F46047888CD63E7960CC94020685FE at srvrcpexchange.mcb_corp.mcbrideelectric.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Martyn,
>
> What input-capable file(s) do you have?
>
> Primary, secondary, and/or designer?
>
> Thanks.
>
> David Morrison
> IT Department
> DMorrison at mcbrideinc.com | www.mcbrideinc.com
>
>
> -----Original Message-----
> From: powerh-l-bounces+dmorrison=mcbrideelectric.com at lists.sowder.com
> [mailto:powerh-l-bounces+dmorrison=mcbrideelectric.com at lists.sowder.com]
> On Behalf Of Thomson, Martyn EDUC:EX
> Sent: Thursday, December 18, 2008 2:15 PM
> To: Ken at Langendock.com; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] The current data will be lost. Repeat the action if
> thisis okay
>
> I am using a cluster so removed all LETs - no difference. No ITEM
> statements.
> Do DEFAULT option on FIELD statements have the same effect?
> Also added an INPUT proc to the temp field to trap it in debug. The
> predefs ALTEREDRECORD, NEWRECORD were both false.
>
>
> -----Original Message-----
> From: Ken Langendock [mailto:ken.langendock at rogers.com]
> Sent: Thu 18-Dec-08 12:25 PM
> To: Thomson, Martyn EDUC:EX; powerh-l at lists.sowder.com
> Subject: RE: [Bulk] The current data will be lost. Repeat the action if
> this is okay
>
> I'll bet you have a let statement somewhere that you think is to a temp
> but
> isn't or something similar.
> I have also found this using an ITEM xxxx FINAL "something".
> Normally this doesn't do anything to records status....but As part of a
> cluster it WILL CHANGE THE RECORD STATUS.
>
> You can't suppress any messages like that, they are there an integral
> part
> of PH.
>
> Ken
>
> -----Original Message-----
> 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 Thomson, Martyn EDUC:EX
> Sent: December 18, 2008 2:33 PM
> To: powerh-l at lists.sowder.com
> Subject: [Bulk] The current data will be lost. Repeat the action if this
> is
> okay
>
> Hi Listers,
> Have a screen where user retrieves existing records for
> viewing/update/entry. They can enter "99" to go to a temporary field and
> submit a batch job to process the records saved/viewed.
> If they attempt to backout from the temp field get message "The current
> data
> will be lost. Repeat the action if this is okay".
>
> Why is this if they have not entered/changed any data or have already
> committed changes? ALTEREDRECORD is FALSE.
> Is this just an automatic warning whenever "^" is entered?
> Is there any way to suppress this msg when it's not relevant?
>
> TIA for any advice.
> Martyn
> PH 7.10G1; OpenVMS Alpha V8.3, Oracle Rdb V7.2-311
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.552 / Virus Database: 270.9.19/1854 - Release Date:
> 17/12/2008
> 7:21 PM
>
>
> No virus found in this outgoing message.
> Checked by AVG.
> Version: 7.5.552 / Virus Database: 270.9.19/1854 - Release Date:
> 17/12/2008
> 7:21 PM
>
>
>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
>
>
> ------------------------------
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
> End of powerh-l Digest, Vol 43, Issue 13
> ****************************************
>
More information about the powerh-l
mailing list