System-maintained field weirdness

[Bruce Easton]

Bruce Easton wrote Friday, October 19, 2007 3:07 PM:
>
> Nancy Palmquist wrote Friday, October 19, 2007 2:55 PM:
> > Kenneth Brody wrote:
> > > 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?
> > >
> >
> > But he said that @ub is not blank but @ud is blank.  Wouldn't they both
> > be filled at the same time?
> >
> > Nancy
> >
>
> But if the records were created from a report process and then only
> batch-updated from another report process, could that leave them
> in the current status?
>
> Bruce
>
> Bruce Easton
> STN, Inc.
>

Well, I ran some tests and confirmed that @ub and @bd are set upon
record creation as well, as Ken indicated for @ub.  So I guess creating
records from a report process and any subsequent report processes
without any direct updating of the records will result in the
status of:

@cb (having something)
@cd (having something)
@bd (having something)
@ub (having something)

and @ud = blank

Bruce

Bruce Easton
STN, Inc.




Bruce

Bruce Easton
STN, Inc.