System date behavior wish (GRX)

[John Esak]

Interesting! I had never thought about a flag for filePro's COPY command
(and I suppose COPYIN as well. I dont' think this would be difficult to do.
I do think it would be a great idea.  It would be great to put records from
one file into a history file without losing the system maintained field
values. Everyone has wanted this for years I think.

Very good suggestion.

John Esak


> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com]On
> Behalf Of Chris Sellitto
> Sent: Monday, February 12, 2007 9:20 AM
> To: filepro-list at lists.celestial.com
> Subject: System date behavior wish (GRX)
>
>
>
> All,
>
> I don't know (or remember) if this topic has been broached in the
> past, but here goes.  I was wondering how difficult it would be
> to have the @system date fields retain their values upon copying
> new records.  I know it would be just as easy carrying a date
> field on the record, but I feel this is an inefficient way of
> doing things, not to mention a waste of field space.  We archive
> our data here on a regular basis, and having this option would be
> great.  Maybe have a new flag on the copy command that would
> instruct filePro to retain its system dates (@cd, @ud, @bd).
>
> Hopefully others out there feel the way I do.  I don't know how
> difficult it would be, but I think it would make a great feature.
>
>
> Thank you
> Christopher Sellitto
> VP Computer Operations
> Guaranteed Returns
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list