"Created by" system maintained field (@cb)

GCC Consulting gccconsulting at comcast.net
Tue Mar 31 18:27:38 PDT 2009



> -----Original Message-----
> From: filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com
>
[mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com]
On
> Behalf Of Kenneth Brody
> Sent: Tuesday, March 31, 2009 4:41 PM
> To: Del
> Cc: filePro Mailing List
> Subject: Re: "Created by" system maintained field (@cb)
> 
> Del wrote:
> > @cb is the "created by" field maintained by filepro for every record in
a
> database.
> > One of my users is complaining that when he modifies an existing record
> created by someone else, it changes the "created by" id to his id, when it
should
> only change @ud (updated by).
> > This is an order entry application and these fields are important to the
way
> they track things.
> > Has anybody else seen this happen?  I thought this field (@cb) would
never
> change once the record is created.  He also reports the @cd (created date)
> does NOT change.
> > Of course, I have not seen this happen myself, and he admits that it
only
> happens occasionally, not every time, so maybe there is another
explanation?
> 
> filePro will only set @CB and @UB when creating a new record.  In the over
> 25 years since Profile/filePro first came out, I do not recall ever having
> heard of it doing otherwise.
> 
> If it only happens "occasionally", I would suspect that on those
> "occasions", the user has, in fact, deleted and recreated a new record,
and
> not updated an existing record.  Is there any pattern?
> 
> --
> Kenneth Brody

Now this is not a problem on the Windows system, These fields @cb and @ub
don't exist.

I manually have to add these fields in file where this is important.  

In fact, I am about to add these to a file which will need to track who
entered the information.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net
  






More information about the Filepro-list mailing list