Re: checking if a delete occurs

[Booth Martin <booth@xxxxxxxxxxxx>]

Here is another choice might work for you:

Each record has a RRN (relative record number) which is unique.  You can 
retrieve this number when you read the record from the file, and store 
the number as a hidden field in the subfile record.  Then, have another 
F-Spec for the same file, unkeyed, and chain to the second file with the 
RRN for update, add, and deletes.





Phil Kestenbaum wrote:
> HI I have a program that displays records in a subfile, there is a not
> very unique key so that in order to allow for Change, Add.  and Delete,
> I set up a logical for the delete and changes.
>
> The record is to simplify:
>
>  
>
> Acct       comment
>
>  
>
> The key is Acct.
>
>  
>
>  
>
> There file is this not unique. There are many same accounts w/ various
> comments.
>
> The user would be able to change the comment field, although mostly they
> are adding comments.
>
> So to make a change you cannot know  which record is needed to change
> since there are many w/ same acct#. I therefore made a logical file of
> acct and comment.
>
>  
>
> (there are many other fields in this file). Thus for same acct-comment
> key we can do a READE and change it on all, although it would be
> unlikely for such a case.
>
>  
>
> The issue is that when you Chain to the file w/ the changed comment
> field, it is not found, in this case there seems to be a 2 step process.
> First to delete the old record having saved the comment, and then to add
> the new record. But I am finding that the Delete is not working. I start
> another session and check the record count and it is not 1 less. So I
> wanted to debug this condition as to why the delete is not working. 
>
>  
>
> Any ideas would be greatly appreciated,
>
> Thank you,
>
> Phil
>
>  
>
>  
>
>
> This message contains information proprietary to our company. It is intended to 
> be read only by the individual or entity named above or their designee.
> Any distribution of this message or the information contained herein without 
> written permission from our company is strictly prohibited. If the reader of 
> this message is not the intended recipient or an agent responsible for 
> delivering it to the intended recipient, you are hereby notified that you have 
> received this document in error and that any review, dissemination, 
> distribution, or copying of this message is strictly prohibited. If you have 
> received this communication in error, please notify us immediately by e-mail, 
> and delete the original message.