Re: Record processing knowledge of dbAccess context

[Marty Kraimer <mrk@aps.anl.gov>]

I think he is asking a more generic question but maybe I am wrong.

PUTF only determines is a record is being processed becaise a dbPutField 
was directed to the record which has PUTF true.

If the dbPutField causes a set of records to be processed the other 
records will not have PUTF true.

A record can be processed for many reasons:

An input link in another record has PP true.
Another record has a forward link to the record.
An ouput link in another record has PP true.
A dbPutField occurs in this record.

PUTF was invented for reprocessing a record if a dbPutField is directed 
to a record while it is active so that it can be reprocessed when the 
record completes processing.

Marty

J. Frederick Bartlett wrote:

> Marty,
>
>  I am somewhat confused by your answer to Peregrine. I had thought the PUTF
> field of a record, which is described in the "Record Reference Manual" as
> "Did dbPutField cause the current record processing", is exactly what
> Peregrine is looking for.
>
> 									Fritz
>
>  
>
> > -----Original Message-----
> > From: Marty Kraimer [mailto:mrk@aps.anl.gov]
> > Sent: Thursday, April 08, 2004 1:07 PM
> > To: Peregrine M. McGehee
> > Cc: tech-talk@aps.anl.gov
> > Subject: Re: Record processing knowledge of dbAccess context
> >
> >
> >
> >
> > Peregrine M. McGehee wrote:
> >
> >    
> >
> > > Dear all,
> > >
> > > Is there any mechanism by which a record can determine the
> > > reason for it being processed, i.e. can it distinguish between
> > > a dbGet and dbPut to the same field?
> > >
> > > A look into the code suggests the answer is "No", but I'd
> > > thought I'd ask.
> > >
> > > Best regards,
> > >    Peregrine
> > >      
> > No.
> >
> >
> >    
>
>