great new wish list item, but how will it really work?

[Joe Chasan]

On Thu, Apr 22, 2004 at 08:24:09AM -0400, John Esak wrote:
> 
> Joe Chason submitted a great wish list item. I voted for it being a
> "must-have". He suggests a new command like COPY called MOVE. It would do
> just that, MOVE a filePro record from one database to another and DELETE it
> from the original file. The difference being that system maintained fields
> would be "maintained" across the move. That is @cd, @ub, etc, would not be
> lost. Very important for archiving... but, the question arises... How can
> you maintain the @cd for example in the new file, when the record needs an
> @cd for that file, itself??
> 
> I often look at my archive invoice file by @cd to see which were the very
> last records just added to it and on what day...  How would I be able to do
> this if the original @cd was kept with the new MOVE command.  JOe?
> 
> I want/need your suggested command, as you do, but how can we deal with the
> reality of how filePro works?  Just lose the @cd of the MOVE'd record in the
> new file??

In your example, if archive invoce file is never deleted from then looking 
at by record # should have same effect.

I would have prefered to keep the original @cd, but i guess you can make
a case for wanting the new @cd of the move  -  i guess its up to the powers
that be @ fp - if they ever decide to implement this - whether the entire
set of internal system maintained fields should be kept in tact or whether
they should allow partial changes.

if to allow partial changes, how about something like 
MOVE xyz WITH (system,maintained,fields)|ALL
e.g. optional breakdown of certain fields or ALL - but if @CD was chosen,
@CB would be implied, same for @UD/@UB
 
--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
-Joe Chasan-                      Magnatech Business Systems, Inc.
joe at magnatechonline.com           Hicksville, NY - USA
http://www.MagnatechOnline.com    Tel.(516) 931-4444/Fax.(516) 931-1264