Fw: one record overwrites another record

[Dennis Malen]

We now have confirmed how the record is being changed.

If someone is in record 1 in update and someone is in record 2. Record 2 
presses <O> to be transferred to record 1 and once record one is unlocked 
record 1's data is transferred into record 2.

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "Dennis Malen" <dmalen at malen.com>
To: <filepro-list at lists.celestial.com>
Cc: <joe at magnatechonline.com>
Sent: Monday, September 18, 2006 4:13 PM
Subject: one record overwrites another record


>H E L P!!!!!
> We have just gone live with 5.0.14D4 from 4.8
>
> We are on AIX 5.3
>
> As of Friday on the filepro 4.8 system all records were intact and 
> correct. We know this as the 4.8 system is still up and running and the 
> problem records in 5.0 are correct in 4.8. We know this problem took place 
> Monday morning.
>
> Monday morning when employees started using the new system we found one 
> record which was incorrect.
>
> By way of background, our screen provides a field 3 which equals @rn when 
> the record is created. We did this years ago in order to be able to tell 
> if a record was changed. We never had a problem until this conversion.
>
> Record 134820 and record 137797 are the problems. Record 137797 was 
> overwritten and now duplicates record 134820 in every way including 
> creation date (@cd). Record 134820 was originated in June (@cd) and record 
> 137797 was originated in September. Now both records show the same 
> identical information including the creation dates.
>
> All records before and after 137797 show the correct creation dates of 
> September. 134820 is the correct record and is no problem. It is only the 
> 137797 which now is identical to 134820 and is wrong.
>
> Lastly, no one with changing rights was in the file. The only thing that 
> did occur was that the person was in 137797 before it changed. Then he did 
> a name search using a user created lookup (lookup - with @key) which takes 
> them to the highlighted record if they press enter. All employees have 
> used this daily in the past with no problem. He then pressed enter and 
> went into 134820. Completed work on 134820. Then used a user lookup 
> (lookup -) by record number (using @rn) and went back to 137797. When 
> there he noticed that 137797 now mirrored 134820. The original record 
> information in 137797 was no where to be found.
>
> We can't ell at what point in the process record 137797 was changed. It 
> probably happened when he went to or from the record using the user 
> processing name search or user processing record number lookup.
>
> Any help would be appreciated.
>
> Dennis Malen
> 516.479.5912