System-maintained field weirdness

[Bruce Easton]

Jean-Pierre A. Radley Friday, October 19, 2007 3:20 PM:

> 
> Ken Brody propounded (on Fri, Oct 19, 2007 at 02:51:40PM -0400):
> | Quoting Jean-Pierre A. Radley (Fri, 19 Oct 2007 14:39:41 -0400):
> | 
> | > On a system running filePro 04.05.08, I am trying to track down why a
> | > certain file occasionally has duplicate records.  One oddity is that
> | > the duplicates will have proper and logical @cb, @cd, and @ub values
> | > but @ud is blank.
> | >
> | > What could cause this?
> | 
> | My first thought would be:
> | 
> | Creating the records via lookup-free in *report, and never updating
> | them after the initial creation?
> 
> OK, records are in fact created by a lookup-free.
> 
> Am I right in recalling that IFF a record has never been updated,
> THEN @ub and @ud still get values, namely those in @cb and @cd?
> 
> IAC, why would @ub have a value, but not @ud?
> 
> -- 
> JP

Yeah - it seems like @ub should be blank from just a creation process 
as well, but maybe it is seen as doing double-duty since there is 
no field @bb for "last batch updated by" like there is to parallel 
@bd.

Bruce

Bruce Easton
STN, Inc.