QUICK: "Record has been changed since you found it. (FILE-B*03)"

[Richard Sheehan]

Are you doing a push find again after the delete, or is the user finding 
the record again after the delete?

It sounds like the cluster is not being refreshed before an attempt to 
"add" a record on that cluster line...  possibly.


roger32909 at bellsouth.net wrote:

>OpenVMS ALPHA V7.3-2, Q D E S I G N   (7.10.G1)
>Copyright 1998 COGNOS INC. (ALPHA)
>Licensed PH-AXP-DEVELOPMENT 
>
>We have a screen with a DETAIL file FILE-A that OCCURS 6 TIMES.
>
>Then there is a SECONDARY file FILE-B that OCCURS with FILE-A.
>which is opened for UPDATE only, NODELETE and NOITEMS.
>
>Some fields in this secondary file are updated when a new
>FILE-A record is created or changed.  The data in these fields
>must be removed in event a FILE-A record is deleted.
>This works fine.
>
>There are also two REFERENCE files FILE-C and FILE-D that OCCUR with FILE-B.
>
>But a problem occurs when a FILE-A record is deleted.  Even after update,
>the OCCURRENCE for this deleted record is apparently still there,
>hence a mostly blank line in the cluster.  I say mostly blank,
>because a field displayed from FILE-B remains even after the
>related FILE-A record is deleted.
>And then, if the user attempts to add a FILE-A record using the same
>key from the deleted FILE-A record, an error message displays:
>"Record has been changed since you found it. (FILE-B*03)"
>
>How can we clear the buffers or break the "link" between this deleted DETAIL record in FILE-A
>and the SECONDARY FILE-B record so the user can enter a FILE-A record
>with the same key as the deleted DETAIL FILE-A record without getting
>an error message?
>
>  
>

-- 
Richard Sheehan
IT Programmer Analyst
208-282-4430
Office of Institutional Research
Idaho State University
Pocatello, ID  83209-8368